Message ID | CACRpkdasaP_xVfQtzq29UNJBXetrUUzqpn90T6_Gr0kOsV8GeQ@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Thu, Oct 18, 2012 at 8:39 PM, Linus Walleij <linus.walleij@linaro.org> wrote: > Hi ARM SoC folks, > > here are two small commits for v3.8 that I'd like to make sure > land in ARM SoC before I begin with all the other stuff. > > Please pull them in! Ping on this. Yours, Linus Walleij
On Thursday 25 October 2012, Linus Walleij wrote: > On Thu, Oct 18, 2012 at 8:39 PM, Linus Walleij <linus.walleij@linaro.org> wrote: > > > Hi ARM SoC folks, > > > > here are two small commits for v3.8 that I'd like to make sure > > land in ARM SoC before I begin with all the other stuff. > > > > Please pull them in! > > Ping on this. Sorry for the delay, I just took over the task to pull in stuff from Olof and we were both busy otherwise earlier. I pulled this into a next/soc branch now. Wasn't completely sure which branch to use but I figured that we couldn't make a good prediction of the ordering yet, and we'll probably have a next/soc2 branch later anyway. Please remember to write the pull request in a way that lets us reuse some of the text for the merge changeset comment. Ideally in a signed tag so git puts it in there automatically. Arnd
On Thu, Oct 25, 2012 at 3:44 PM, Arnd Bergmann <arnd@arndb.de> wrote: > Please remember to write the pull request in a way that lets us reuse some > of the text for the merge changeset comment. Ideally in a signed tag > so git puts it in there automatically. So what was wrong with this signed tag, looking like that? ---------------------------------------------------------------- A first set of Ux500 core patches for v3.8: - Support the HREF520 board - Add the device serial number to the entropy pool ---------------------------------------------------------------- I guess what I'm after is what makes it reusable if this one isn't. Yours, Linus Walleij
On Thursday 25 October 2012, Linus Walleij wrote: > On Thu, Oct 25, 2012 at 3:44 PM, Arnd Bergmann <arnd@arndb.de> wrote: > > > Please remember to write the pull request in a way that lets us reuse some > > of the text for the merge changeset comment. Ideally in a signed tag > > so git puts it in there automatically. > > So what was wrong with this signed tag, looking like that? > > ---------------------------------------------------------------- > A first set of Ux500 core patches for v3.8: > - Support the HREF520 board > - Add the device serial number to the entropy pool > > ---------------------------------------------------------------- > > I guess what I'm after is what makes it reusable if this one > isn't. The tag looks great, but you were sending the pull request for the branch "ux500-core", not for the tag "ux500-core-for-arm-soc". This has happened to me a few times before, especially when pushing the tag just before sending the pull request. In that case, git-request-pull cannot find the tag on the server because it has not been mirrored back from the git+ssh server to the publically accessible one that it reads the tags from. Arnd
On Thu, Oct 25, 2012 at 5:13 PM, Arnd Bergmann <arnd@arndb.de> wrote: > The tag looks great, but you were sending the pull request for > the branch "ux500-core", not for the tag "ux500-core-for-arm-soc". > > This has happened to me a few times before, especially when pushing > the tag just before sending the pull request. In that case, > git-request-pull cannot find the tag on the server because it has > not been mirrored back from the git+ssh server to the publically > accessible one that it reads the tags from. Ah yes this mirror thing is a bit dangerous, I usually check it by inspecting the warning message that request-pull generates, but must've missed it. Yours, Linus Walleij