From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] first set of ux500 for ARM SoC for v3.8
Date: Thu, 25 Oct 2012 15:13:43 +0000 [thread overview]
Message-ID: <201210251513.43931.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdZ9fUUugHAPGw8kEZDFnDWyyZ-b2iUdfCu2Hhhg4swaPQ@mail.gmail.com>
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
next prev parent reply other threads:[~2012-10-25 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 18:39 [GIT PULL] first set of ux500 for ARM SoC for v3.8 Linus Walleij
2012-10-25 7:22 ` Linus Walleij
2012-10-25 13:44 ` Arnd Bergmann
2012-10-25 14:37 ` Linus Walleij
2012-10-25 15:13 ` Arnd Bergmann [this message]
2012-10-25 15:58 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201210251513.43931.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.