From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [GIT PULL] devicetree changes for v3.3
Date: Mon, 16 Jan 2012 09:21:42 -0700 [thread overview]
Message-ID: <20120116162142.GE4223@ponder.secretlab.ca> (raw)
In-Reply-To: <CA+55aFzWaKBQU-XRYtu0WGq1328nX3hbHDjcn3etOTPsyA=xcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sat, Jan 07, 2012 at 12:41:25PM -0800, Linus Torvalds wrote:
> On Wed, Jan 4, 2012 at 11:11 PM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> > Hi Linus,
> >
> > Please pull the following device tree changes queued up for 3.3.
> >
> > There is a signed tag for this pull request: devicetree-for-linus-20120104
> >
> > The following changes since commit 805a6af8dba5dfdd35ec35dc52ec0122400b2610:
> >
> > Linux 3.2 (2012-01-04 15:55:44 -0800)
> >
> > are available in the git repository at:
> > git://git.secretlab.ca/git/linux-2.6 devicetree/merge
>
> Ok, so I pulled the tags, but only because I noticed that you mentioned it.
>
> It would have been much more convenient if you had just named the tag
> in the pull request directly, so that it would have said
>
> > are available in the git repository at:
> > git://git.secretlab.ca/git/linux-2.6 devicetree-for-linus-20120104
>
> and then my normal "cut-and-paste the pull request line" JustWorks(tm).
>
> Of course, since you use those ugly tag names, I then end up editing
> the first line so that the shortlog doesn't fill up with random crud,
> so I'd actually prefer for the tag-name to not have that silly date in
> it. The tag itself is dated, so the date information actually does
> exist inside of it - and if I pull the signed tag, it will then exist
> hidden in the merge too (and can be shown using the new "git show
> --show-signature" thing):
Okay, will do.
g.
prev parent reply other threads:[~2012-01-16 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 7:11 [GIT PULL] devicetree changes for v3.3 Grant Likely
[not found] ` <CACxGe6udggDJ2QCRXGKzPwHUwzPsFLPZ1Ogc-Negx9z=UHEntg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-07 20:41 ` Linus Torvalds
[not found] ` <CA+55aFzWaKBQU-XRYtu0WGq1328nX3hbHDjcn3etOTPsyA=xcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-16 16:21 ` Grant Likely [this message]
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=20120116162142.GE4223@ponder.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).