From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] block fixes for 3.9-rc
Date: Fri, 29 Mar 2013 12:24:11 -0600 [thread overview]
Message-ID: <20130329182411.GD2567@kernel.dk> (raw)
In-Reply-To: <CA+55aFwoj=g0YrFOrpoKNY43o8qDAhDEHSP-zrtpWCXciwz_-Q@mail.gmail.com>
On Fri, Mar 29 2013, Linus Torvalds wrote:
> On Fri, Mar 29, 2013 at 8:38 AM, Jens Axboe <axboe@kernel.dk> wrote:
> >
> > Please pull! As per usual, it's tagged and signed.
>
> No it's not.
>
> You have a *branch* called for-linus that contains the commits you mention.
>
> And then you have a *tag* called for-linus, but that's just my old
> head that you've gone ahead and signed, which is entirely and utterly
> pointless.
Oops, that was a mistake. I must have been on the wrong branch at that
point. In past requests, I've signed the for-linus (or topic) branch
specifically.
> Christ, the amount of confusion in that tree. Don't alias tags and
> branches. And if you do, make it clear which one you mean by *saying*
> so, ie "tags/for-linus", not just the ambiguous "for-linus". Now
> you've confused yourself, and because of the ambiguity you never even
> noticed, because the *branch* for-linus had the right commits.
Agree, the aliasing is nasty and git checkout usually doesn't like it a
whole lot either...
> Don't do this kind of thing. That branch is pointless, and just
> confused you.
Tag, you mean?
--
Jens Axboe
next prev parent reply other threads:[~2013-03-29 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 15:38 [GIT PULL] block fixes for 3.9-rc Jens Axboe
2013-03-29 18:08 ` Linus Torvalds
2013-03-29 18:24 ` Jens Axboe [this message]
2013-03-29 18:47 ` Linus Torvalds
2013-03-29 19:00 ` Jens Axboe
2013-03-29 19:57 ` Linus Torvalds
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=20130329182411.GD2567@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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