From: Lachlan McIlroy <lachlan@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: Re: [GIT PULL] XFS update for 2.6.27
Date: Thu, 31 Jul 2008 14:59:42 +1000 [thread overview]
Message-ID: <489146BE.6020308@sgi.com> (raw)
In-Reply-To: <20080731034952.GC13395@disturbed>
Dave Chinner wrote:
> On Thu, Jul 31, 2008 at 12:53:28PM +1000, Lachlan McIlroy wrote:
>> The following changes since commit c9272c4f9fbe2087beb3392f526dc5b19efaa56b:
>> Linus Torvalds (1):
>> Merge branch 'hotfixes' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6
>>
>> are available in the git repository at:
>>
>> git://oss.sgi.com:8090/xfs/xfs-pull for-linus
> .....
>> Lachlan McIlroy (11):
>> [XFS] Use the generic xattr methods.
> .....
>> [XFS] Use the generic xattr methods.
>
> BTW, that's a patch from Christoph, so there's a mistake in the
> author of that patch. I don't know why there's duplicates of it
> in the tree - the only thing I can see is that the committer's
> email address is not stable. There is a growing number of
> duplicate commits like this in the XFS tree.....
>
Yeah I know there are problems with the merge scripts. Christoph
had already pointed this one out and I thought it had been corrected.
I just don't have the time to fix every commit that comes through.
next prev parent reply other threads:[~2008-07-31 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 2:53 [GIT PULL] XFS update for 2.6.27 Lachlan McIlroy
2008-07-31 3:49 ` Dave Chinner
2008-07-31 4:59 ` Lachlan McIlroy [this message]
2008-08-01 19:02 ` Christoph Hellwig
2008-07-31 4:09 ` Eric Sandeen
2008-07-31 5:11 ` Lachlan McIlroy
2008-07-31 5:36 ` Lachlan McIlroy
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 7:58 Lachlan McIlroy
2008-09-26 5:52 Lachlan McIlroy
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=489146BE.6020308@sgi.com \
--to=lachlan@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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