public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: markgw@sgi.com
Cc: Eric Sandeen <sandeen@sandeen.net>, lachlan@sgi.com, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.25-rc4
Date: Fri, 29 Feb 2008 18:39:46 +1100	[thread overview]
Message-ID: <47C7B6C2.4030304@sgi.com> (raw)
In-Reply-To: <47C7A92C.10007@sgi.com>

Mark Goodwin wrote:
> 
> 
> 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?
> 
Yes it would.
One needs the signed-off-by's.
 From our sgi internal web page...

==============================================================================
Bad ptool checkin descriptions

Bad checkin descriptions for XFS to ptools are ones which are missing a one
line overall description and ones where the mod has an external author and
there is no Signed-Off-By lines for him/her.

So what you need to have is:...
The first line to be a summary description.  Then if you need further details,
then add a blank line followed by more details in further paragraphs.
Then end with the signed-off-by's.  The script needs signed-off-by to determine
real author and Linus uses the first line as a summary line in his summary code.

The script will look at the ptools mod reviewer list to add in further
signed-off-by's when it gets converted to git.  So you only need 1 signed-off-by
for the external author and if it is just an internal author, you don't need any
signed-off-bys.  (And yes ideally, the reviewers should probably be acked-by...
it is on the TODO list).
==============================================================================

--Tim

  parent reply	other threads:[~2008-02-29  7:39 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
2008-02-29  6:59         ` Lachlan McIlroy
2008-02-29  7:39         ` Timothy Shimmin [this message]
  -- 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=47C7B6C2.4030304@sgi.com \
    --to=tes@sgi.com \
    --cc=lachlan@sgi.com \
    --cc=markgw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox