From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: 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: Wed, 21 Jun 2006 15:51:34 -0700 [thread overview]
Message-ID: <20060621225134.GA13618@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606211519550.5498@g5.osdl.org>
On Wed, Jun 21, 2006 at 03:22:19PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 21 Jun 2006, Greg KH wrote:
> >
> > 123 files changed, 4169 insertions(+), 2440 deletions(-)
>
> Btw, I get
>
> 119 files changed, 3888 insertions(+), 2159 deletions(-)
>
> Why? Becuause my default pull script has rename detection enabled, and I
> get:
>
> rename include/linux/{usb_cdc.h => usb/cdc.h} (100%)
> rename include/linux/{usb_input.h => usb/input.h} (100%)
> rename include/linux/{usb_isp116x.h => usb/isp116x.h} (100%)
> rename include/linux/{usb_sl811.h => usb/sl811.h} (71%)
>
> which explains the off-by-four number (and the smaller number of
> lines changed).
>
> Just out of interest, could you enable that in your scripts too, so that
> renames don't show up as huge deletes/creates (well, in this case, thet
> were pretty small files, but you get the idea)?
Ok, but how? I'm generating the diffstat in my script with:
git diff origin..HEAD | diffstat -p1 >> $TMP_FILE
Is there a better way to see these renames? In playing around with 'git
diff' I didn't see how to do it, but I'm probably just not looking for
the right option...
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-21 22:54 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 [this message]
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
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=20060621225134.GA13618@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