public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bugfixes for 3.2-rc5
Date: Tue, 20 Dec 2011 21:37:50 -0800	[thread overview]
Message-ID: <7v8vm6iixd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vd3biijdc.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 20 Dec 2011 21:28:15 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Ted Ts'o <tytso@mit.edu> writes:
> ...
>> And this isn't in 1.7.8 yet, right?  I'd have to build version of git
>> based on the next branch to play with this new signatury goodness?
>
> The 'master' branch as of this week has the topic merged.

Also please notice that the original "pull request" said:

    Hi Linus,

    There is a signed tag tytso-for-linus-20111214 covering these patches,...
    Please pull,

                                                    - Ted

    The following changes since commit dc47ce90c3a822cd7c9e9339fe4d5f61dcb26b50:

      Linux 3.2-rc5 (2011-12-09 15:09:32 -0800)

    are available in the git repository at:
      git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev

    Andrea Arcangeli (1):
          ext4: avoid hangs in ext4_da_should_update_i_disksize()
    ... shortlog output ...

that mentions where the work forked, but does _not_ mention what tip
commit of "dev" branch to expect. Updated "git request-pull" command will
have that information, and also gives the tag name you already pushed out
to your publishing repository instead of the branch name "dev" when
producing the "... available in the git repository at:" information.

  reply	other threads:[~2011-12-21  5:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 19:20 [GIT PULL] ext4 bugfixes for 3.2-rc5 Theodore Ts'o
2011-12-15  2:50 ` Linus Torvalds
2011-12-15 19:08   ` Ted Ts'o
2011-12-15 22:13     ` Linus Torvalds
2011-12-21  5:28     ` Junio C Hamano
2011-12-21  5:37       ` Junio C Hamano [this message]
2011-12-21  5:41   ` Junio C Hamano
     [not found] <i82GC-j4-7@gated-at.bofh.it>
     [not found] ` <i89I5-3Bp-11@gated-at.bofh.it>
     [not found]   ` <i8oQP-4s2-29@gated-at.bofh.it>
     [not found]     ` <i8rOG-XY-7@gated-at.bofh.it>
2011-12-17  8:20       ` Nick Holloway

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=7v8vm6iixd.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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