public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: unlisted-recipients:; (no To-header on input)
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.17
Date: Thu, 22 Jun 2006 11:30:21 -0700	[thread overview]
Message-ID: <20060622183021.GA5857@kroah.com> (raw)
In-Reply-To: <20060622181826.GB22867@kroah.com>

On Thu, Jun 22, 2006 at 11:18:26AM -0700, Greg KH wrote:
> On Wed, Jun 21, 2006 at 06:22:58PM -0700, Linus Torvalds wrote:
> > And as usual, the diff options work fine with "git log" too, so you can do
> > 
> > 	git log -M --stat --summary
> > 
> > and it will do the right thing. Look at your ae0dadcf.. commit, for 
> > example.
> > 
> > Btw, the _one_ thing to be careful about is that when you generate a real 
> > patch with "-M", if that patch actually has a rename, then only "git 
> > apply" will be able to apply it correctly, and if somebody uses a regular 
> > "patch" program to apply it, they'll miss out on the rename, of course.
> > 
> > Some day maybe the git "extended patch format" is so univerally recognized 
> > to be superior that everybody understands them, in the meantime you may 
> > not want to use "-M" to generate patches unless you know the other end 
> > applies them with git.
> > 
> > (Which also explains why "-M" is not the default, of course).
> 
> For now I'll leave -M off, as people might want to apply the patches
> from email.  Although it might cut down on main bandwidth, and they can
> always refer to the git tree or original patch...  I'll think about that
> one.

I take that back.  I just used -M for the W1 patch series and I think it
is very helpful as it shows only the lines that change in a rename,
which can easily get lost in the noise of a longer patch.

Very nice stuff, have I mentioned lately how much I love git?

thanks,

greg k-h

  reply	other threads:[~2006-06-22 18:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 22:06 [GIT PATCH] USB patches for 2.6.17 Greg KH
2006-06-21 22:22 ` Linus Torvalds
2006-06-21 22:51   ` Greg KH
2006-06-22  0:51     ` Linus Torvalds
2006-06-22  1:22     ` Linus Torvalds
2006-06-22 18:18       ` Greg KH
2006-06-22 18:30         ` Greg KH [this message]
2006-06-22 18:49           ` Randy.Dunlap
2006-06-22 18:54             ` Greg KH
2006-06-23  5:52               ` Evgeniy Polyakov
2006-06-23  6:07                 ` Greg KH
2006-06-22 19:50           ` Linus Torvalds
2006-06-22 20:01             ` Sam Ravnborg
2006-06-22 20:52               ` Petr Baudis
2006-06-22 21:01               ` Linus Torvalds
2006-06-22 21:07                 ` Linus Torvalds
2006-06-22 23:11 ` Linus Torvalds
2006-06-22 23:40   ` Greg KH
2006-06-22 23:48     ` Linus Torvalds
2006-06-22 23:52       ` Greg KH
2006-06-23  0:32         ` Andrew Morton
2006-06-23  0:41           ` Greg KH
2006-06-23  0:05     ` Jeremy Fitzhardinge
2006-06-23  0:17       ` Andrew Morton
2006-06-23  0:22         ` Greg KH
2006-06-23  0:38           ` Greg KH
2006-06-23  0:56   ` Greg KH

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=20060622183021.GA5857@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@osdl.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