linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: Regulator update for 3.3
Date: Mon, 30 Jan 2012 18:51:50 +0000	[thread overview]
Message-ID: <20120130185150.GA6684@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CA+55aFxPivRzaKaNnTseyWmRhfvxV1=gWSTzgmSZx5Nm8XK=zg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

On Mon, Jan 30, 2012 at 10:22:28AM -0800, Linus Torvalds wrote:
> On Mon, Jan 30, 2012 at 9:43 AM, Mark Brown

> > tags or not.  Either that or complain bitterly and mock me if I'm so
> > foolish as to have a tag and branch with the same name.

> I won't mock you (*this* time), but I think the "tags/for-linus"
> approach is better, as it should work regardless of git version.

Yes, indeed - so probably git request-pull ought to just do that when
working with a tag (which I guess it knows it's doing because it managed
to add the information it pulled from the tag into the pull request)
since it'll help with old versions and avoids confusions like this.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-01-30 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 13:42 Regulator update for 3.3 Mark Brown
2012-01-30 17:14 ` Linus Torvalds
2012-01-30 17:43   ` Mark Brown
2012-01-30 18:22     ` Linus Torvalds
2012-01-30 18:51       ` Mark Brown [this message]
2012-02-01  5:00         ` Junio C Hamano
2012-02-01  9:54           ` Mark Brown

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=20120130185150.GA6684@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).