public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	Ben Collins <bcollins@ubuntu.com>,
	Jody McIntyre <scjody@modernduck.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [git pull] ieee1394 tree for 2.6.18
Date: Tue, 20 Jun 2006 03:55:52 +0100	[thread overview]
Message-ID: <20060620025552.GO27946@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0606191902350.5498@g5.osdl.org>

On Mon, Jun 19, 2006 at 07:06:39PM -0700, Linus Torvalds wrote:
> 
> 
> On Sun, 18 Jun 2006, Stefan Richter wrote:
> > 
> > the IEEE 1394 subsystem updates for Linux 2.6.18 are now staged in Ben's
> > revived linux1394 git tree. I guess the URL to pull from is
> > git://git.kernel.org/pub/scm/linux/kernel/git/bcollins/linux1394-2.6.git
> 
> I'm sure that URL works fine, but I want to see what I'm pulling before I 
> pull it, so _please_ use one of the scripts that generates diffstats and 
> shortlogs, or do it by hand..

Hrm...  That's actually one thing git might do - how hard would it be
to teach git-upload-pack to generate the diffstat and shortlog instead
of a pack?  It has all information needed for that, after all...

I mean, _you_ can ask that sort of summary, but when somebody else
wants to take a look at the summary of some branch in remote repository
mentioned on l-k, well...

If that's too much work server-side, could the result of git-fetch-pack -k
be easily postprocessed client-side to get the same result?  That's
easy to undo - just a single rm would do that...

  reply	other threads:[~2006-06-20  2:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 12:03 [git pull] ieee1394 tree for 2.6.18 Stefan Richter
2006-06-20  2:06 ` Linus Torvalds
2006-06-20  2:55   ` Al Viro [this message]
2006-06-20  3:14     ` Linus Torvalds
2006-06-20  4:22       ` Al Viro
2006-06-20  4:31         ` Al Viro
2006-06-20  4:35           ` Roland Dreier
2006-06-20 17:53       ` Russell King
2006-06-20 19:29         ` Stefan Richter
2006-06-20 19:34           ` Russell King
2006-06-20 20:02             ` Dave Neuer
2006-06-20 20:22               ` Al Viro
2006-06-20 21:15                 ` Dave Neuer
2006-06-20 21:40                   ` Linus Torvalds
2006-06-20 20:57             ` Stefan Richter
2006-06-20 21:03               ` Stefan Richter
2006-06-20 21:15               ` Al Viro
2006-06-21 17:08                 ` Ryan Anderson
2006-06-20 21:25         ` Linus Torvalds
2006-06-20 10:38   ` Stefan Richter
2006-06-21  3:07     ` Linus Torvalds
2006-06-21  6:32       ` Ben Collins
2006-06-21  9:49         ` Stefan Richter
2006-06-21 10:27           ` Ben Collins
2006-06-21 12:01           ` Junio C Hamano

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=20060620025552.GO27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=bcollins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=scjody@modernduck.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --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