From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
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:41:12 -0800 [thread overview]
Message-ID: <7v4nwuiirr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CA+55aFw6n=WaDWRn7NqtBei1x0-w1PkH5x6r3iQSSPZvxYvDhQ@mail.gmail.com> (Linus Torvalds's message of "Wed, 14 Dec 2011 18:50:07 -0800")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Dec 14, 2011 at 11:20 AM, Theodore Ts'o <tytso@mit.edu> wrote:
>>
>> There is a signed tag tytso-for-linus-20111214 covering these patches,
>> which fix a potential hang, crash (on big endian), and data corruption
>> bugs which show up when using fsx and/or Hugh's kernel compile/mm
>> torture test.
>
> Ok, since I build my own git versions, I have one that can pull signed
> tags and automatically verifies them and saves the signed tag
> information as part of the commit object.
Just a note. The new feature was broken when the pull has conflict that
needs to be resolved and concluded with "git commit". The version of git
from 'master' as of today should have a fix, but older ones forgot to
record the mergetag in the resulting commit object.
next prev parent reply other threads:[~2011-12-21 5:41 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
2011-12-21 5:41 ` Junio C Hamano [this message]
[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=7v4nwuiirr.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