From: Roland Dreier <rdreier@cisco.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>,
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: Mon, 19 Jun 2006 21:35:31 -0700 [thread overview]
Message-ID: <adar71kphpo.fsf@cisco.com> (raw)
In-Reply-To: <20060620043148.GQ27946@ftp.linux.org.uk> (Al Viro's message of "Tue, 20 Jun 2006 05:31:48 +0100")
> Actually, posting that _was_ useful - staring at the above got me to
> realize that git clone -l -s -n + git fetch + git log + rm -rf would
> work just fine and be much faster than the variant above...
>
> Still, that looks like excessive from server, if nothing else. Is there
> a better way to do it? Getting remote log, that is, preferably with
> a way to get it starting at the point I have in local tree.
In the same vein "git clone --reference <local tree> <remote>" would
be a further optimization, I think.
- R.
next prev parent reply other threads:[~2006-06-20 4:35 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
2006-06-20 4:31 ` Al Viro
2006-06-20 4:35 ` Roland Dreier [this message]
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=adar71kphpo.fsf@cisco.com \
--to=rdreier@cisco.com \
--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 \
--cc=viro@ftp.linux.org.uk \
/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