public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] dlm updates for 2.6.26
Date: Tue, 22 Apr 2008 16:08:47 -0500	[thread overview]
Message-ID: <20080422210847.GB14594@redhat.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0804221344470.2779@woody.linux-foundation.org>

On Tue, Apr 22, 2008 at 01:46:54PM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 22 Apr 2008, David Teigland wrote:
> > 
> > Please pull dlm updates for 2.6.26 from:
> 
> Small detail: can you please use "--stat --summary -M" to generate the 
> diffstat, because you had:
> 
> >  ...
> >  21 files changed, 614 insertions(+), 499 deletions(-)
> 
> but what I then check against notices the rename, and becomes:
> 
>  ...
>  20 files changed, 276 insertions(+), 161 deletions(-)
>  rename fs/{gfs2/locking => }/dlm/plock.c (67%)
>  create mode 100644 include/linux/dlm_plock.h
>  delete mode 100644 include/linux/lock_dlm_plock.h
> 
> which I think is more accurate as to how big the changes were, as well as 
> just more human-readable and informative.
> 
> (Apparently the naming changes in lock_dlm_plock.h -> dlm_plock.h makes it 
> be effectively a rewrite, explaining why it's not two renames..)

Yep, will do.  Nice diffstat for the record,

 fs/dlm/Makefile                   |    1 +
 fs/dlm/config.c                   |   50 +++++++++--
 fs/dlm/config.h                   |    3 +-
 fs/dlm/dlm_internal.h             |    8 +-
 fs/dlm/lock.c                     |    5 +-
 fs/dlm/lock.h                     |    1 -
 fs/dlm/main.c                     |    7 ++
 fs/dlm/member.c                   |   34 +++++++-
 fs/{gfs2/locking => }/dlm/plock.c |  169 ++++++++++++++++++++++---------------
 fs/dlm/recoverd.c                 |    1 +
 fs/gfs2/locking/dlm/Makefile      |    2 +-
 fs/gfs2/locking/dlm/lock_dlm.h    |   12 +---
 fs/gfs2/locking/dlm/main.c        |    8 --
 fs/gfs2/locking/dlm/mount.c       |   21 +++++
 include/linux/Kbuild              |    2 +-
 include/linux/dlm.h               |    7 +-
 include/linux/dlm_device.h        |   11 ++-
 include/linux/dlm_plock.h         |   50 +++++++++++
 include/linux/dlmconstants.h      |    4 +
 include/linux/lock_dlm_plock.h    |   41 ---------
 20 files changed, 276 insertions(+), 161 deletions(-)
 rename fs/{gfs2/locking => }/dlm/plock.c (67%)
 create mode 100644 include/linux/dlm_plock.h
 delete mode 100644 include/linux/lock_dlm_plock.h


      reply	other threads:[~2008-04-22 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 13:51 [GIT PULL] dlm updates for 2.6.26 David Teigland
2008-04-22 20:46 ` Linus Torvalds
2008-04-22 21:08   ` David Teigland [this message]

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=20080422210847.GB14594@redhat.com \
    --to=teigland@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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