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 05:22:51 +0100 [thread overview]
Message-ID: <20060620042250.GP27946@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0606192007460.5498@g5.osdl.org>
On Mon, Jun 19, 2006 at 08:14:45PM -0700, Linus Torvalds wrote:
> But that's not the point.
>
> I want to know what I'm pulling _ahead_ of time, AND I WANT TO KNOW THAT
> WHAT I PULL IS WHAT THE SENDER INTENDED ME TO PULL!
No arguments; that's a different question.
I'm _not_ saying that you should <something>.
I'm saying that often _I_ am curious about the log _in_ _some_ _remote_ _tree_.
Preferably - without fetch + git log + rm .git/refs/tmp + git prune, which
is how I do that now. git prune is quite slow, for one thing...
It's not about kernel or getting stuff merged; the question is about git
and cheaper way to do the thing I often find useful. IOW, read that as
"BTW, is there a way to get such information out of git without too much
PITA?"
next prev parent reply other threads:[~2006-06-20 4:22 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
2006-06-20 3:14 ` Linus Torvalds
2006-06-20 4:22 ` Al Viro [this message]
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=20060620042250.GP27946@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