linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
	Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH 05/11] xfs: set XFS_DA_OP_OKNOENT in xfs_attr_get
Date: Mon, 7 Nov 2016 09:20:27 +1100	[thread overview]
Message-ID: <20161106222027.GN14023@dastard> (raw)
In-Reply-To: <147828423671.31492.10920798285495163593.stgit@birch.djwong.org>

Darrick,

There's something whacky with what you are doing to create these
commit messages. The from address on the email itself is not from
you (how did that get through SPF checks?) and instead there's this:

On Fri, Nov 04, 2016 at 11:30:36AM -0700, Eric Sandeen wrote:
> >From c400ee3ed1b13d45adde68e12254dc6ab6977b59 Mon Sep 17 00:00:00 2001

Which tells me nothing useful about the origin of the patch and it
means I have to mangle the commit message before committing it.

If you look at the libxfs sync commits that I applied for the
4.9-rc1 sync, the libxfs-apply script ends up formating the commits
like this:

ommit ece930fa14a3439e40cd1b43063cab5b85ab9407
Author: Christoph Hellwig <hch@lst.de>
Date:   Tue Oct 25 12:59:46 2016 +1100

    xfs: refactor xfs_bunmapi_cow
    
    Source kernel commit: fa5c836ca8eb5bad6316ddfc066acbc4e2485356
    
    Split out two helpers for deleting delayed or real extents from the COW fork.
    This allows to call them directly from xfs_reflink_cow_end_io once that
    function is refactored to iterate the extent tree.  It will also allow
    to reuse the delalloc deletion from xfs_bunmapi in the future.
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Signed-off-by: Dave Chinner <david@fromorbit.com>


So there's a clear line where the orginal commit came from. It does
this automatically now (see the fixup_header_format() function) so
that this sort of things doesn't need to be cleaned up after the
fact. If the commit is from xfsprogs and going to the kernel, it
will say "Source xfsprogs commit: ....." instead.  This way it is
clear to the reader that this commit is simply a libxfs sync commit,
and that the sob and rvb tags applied to the commit in the source
repository.

Perhaps you are using an older version of the script to generate
these commits?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2016-11-06 22:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 18:30 [PATCH 00/11] xfsprogs: miscellaneous libxfs cleanups Darrick J. Wong
2016-11-04 18:30 ` [PATCH 01/11] xfs_repair: fix some potential null pointer deferences Darrick J. Wong
2016-11-04 18:30 ` [PATCH 02/11] xfs_repair: fix bogus rmapbt record owner check Darrick J. Wong
2016-11-04 18:30 ` [PATCH 03/11] xfs_io: fix libxfs naming violation Darrick J. Wong
2016-11-04 18:30 ` [PATCH 04/11] libxfs: remove unnecessary hascrc test in btree verifiers Darrick J. Wong
2016-11-04 18:30 ` [PATCH 05/11] xfs: set XFS_DA_OP_OKNOENT in xfs_attr_get Eric Sandeen
2016-11-06 22:20   ` Dave Chinner [this message]
2016-11-04 18:30 ` [PATCH 06/11] libxfs: refactor btree crc verifier Darrick J. Wong
2016-11-04 18:30 ` [PATCH 07/11] libxfs: fix whitespace to match the kernel Darrick J. Wong
2016-11-04 18:30 ` [PATCH 08/11] libxfs: return bool from sb_version_hasmetauuid Darrick J. Wong
2016-11-04 18:31 ` [PATCH 09/11] xfs: fix btree cursor error cleanups Brian Foster
2016-11-04 18:31 ` [PATCH 10/11] libxfs: clean up _dir2_data_freescan Darrick J. Wong
2016-11-04 18:31 ` [PATCH 11/11] tools: create libxfs-diff to compare libxfses Darrick J. Wong

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=20161106222027.GN14023@dastard \
    --to=david@fromorbit.com \
    --cc=darrick.wong@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).