From: Mark Goodwin <markgw@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: lachlan@sgi.com, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.25-rc4
Date: Fri, 29 Feb 2008 17:41:48 +1100 [thread overview]
Message-ID: <47C7A92C.10007@sgi.com> (raw)
In-Reply-To: <47C79BD8.4050708@sandeen.net>
Eric Sandeen wrote:
> Lachlan McIlroy wrote:
>> Eric Sandeen wrote:
>>> Lachlan McIlroy wrote:
>>>> Please pull from the for-linus branch:
>>>> git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
>>>>
>>>> This will update the following files:
>>>>
>>>> fs/xfs/linux-2.6/xfs_super.c | 14 +++++++-------
>>>> fs/xfs/xfs_clnt.h | 2 +-
>>>> fs/xfs/xfs_ialloc.c | 2 +-
>>>> fs/xfs/xfs_mount.h | 2 +-
>>>> fs/xfs/xfs_vfsops.c | 4 ++--
>>>> 5 files changed, 12 insertions(+), 12 deletions(-)
>>>>
>>>> through these commits:
>>>>
>>>> commit b7405bb65a83e819dd3b21a6d9636c279d9ce79a
>>>> Author: Niv Sardi <xaiki@sgi.com>
>>> um, I thought Jeff wrote that patch.
>> I'm sure he did too. Every now and then our ptools -> git merge tools stuff up.
>>
>
> IMHO it's worth finding out why; authorship should not be taken lightly.
>
> -Eric
yes I agree. Niv's take:
Inspected by: bnaujok,jeffpc
and no Signed-off
Lachlan, would that have confused the scripts?
--
Mark Goodwin markgw@sgi.com
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
next prev parent reply other threads:[~2008-02-29 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 3:50 [GIT PULL] XFS update for 2.6.25-rc4 Lachlan McIlroy
2008-02-29 4:12 ` Eric Sandeen
2008-02-29 4:56 ` Lachlan McIlroy
2008-02-29 5:44 ` Eric Sandeen
2008-02-29 6:41 ` Mark Goodwin [this message]
2008-02-29 6:59 ` Lachlan McIlroy
2008-02-29 7:39 ` Timothy Shimmin
-- strict thread matches above, loose matches on Subject: below --
2008-02-26 6:49 Lachlan McIlroy
2008-02-26 7:12 ` Eric Sandeen
2008-02-26 7:32 ` 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=47C7A92C.10007@sgi.com \
--to=markgw@sgi.com \
--cc=lachlan@sgi.com \
--cc=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.