archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Mark Brown <>
Cc: Linus Torvalds <>,, Liam Girdwood <>
Subject: Re: Regulator update for 3.3
Date: Tue, 31 Jan 2012 21:00:16 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Mark Brown's message of "Mon, 30 Jan 2012 18:51:50 +0000")

Mark Brown <> writes:

> 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.

I heard you.

I'd appreciate it if you could Bc: either myself or
next time you have improvement suggestions to Git.


  reply	other threads:[~2012-02-01  5:00 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
2012-02-01  5:00         ` Junio C Hamano [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).