[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwwfMTN=WGQGmFO7DYeBUOGA7V4_6XueQS4JAzeykwn3Q@mail.gmail.com>
Date: Fri, 1 Jun 2012 10:19:33 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Theodore Ts'o" <tytso@....edu>
Cc: linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: GIT PULL] ext4 updates for 3.5
On Fri, Jun 1, 2012 at 8:44 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Is there perhaps a tag I should pull instead?
Never mind, I see it. It's 'ext4_for_linus'.
So here's the odd 'git' trick of the day. Do
git ls-remote
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 | less -S
to see all the branches and tags. In there, we see the branch you
asked me to pull:
5e44f8c374.. refs/heads/dev
and then we can see if perhaps any of the tags have that same commit
when peeled. So search for 5e44f8c374, and sure enough:
..
4e4d525149.. refs/tags/ext4_for_linus
5e44f8c374.. refs/tags/ext4_for_linus^{}
..
so that 'ext4_for_linus' tag (which obviously has a different SHA1
than the commit it points to) points to the same commit (the "^{}" is
just the git SHA1 expression for "commit pointed to by object").
So pulling 'ext4_for_linus' instead of 'dev' will get me the same
commits you asked me to pull, with the added tag information that your
pull request containes.
Now I just wonder why your pull request said 'dev' at all.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists