Re: [git pull] ieee1394 tree for 2.6.18
- From: Roland Dreier <rdreier@xxxxxxxxx>
- Date: Mon, 19 Jun 2006 21:35:31 -0700
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [git pull] ieee1394 tree for 2.6.18
- From: Stefan Richter
- Re: [git pull] ieee1394 tree for 2.6.18
- From: Linus Torvalds
- Re: [git pull] ieee1394 tree for 2.6.18
- From: Al Viro
- Re: [git pull] ieee1394 tree for 2.6.18
- From: Linus Torvalds
- Re: [git pull] ieee1394 tree for 2.6.18
- From: Al Viro
- Re: [git pull] ieee1394 tree for 2.6.18
- From: Al Viro
- [git pull] ieee1394 tree for 2.6.18
- Prev by Date: Re: emergency or init=/bin/sh mode and terminal signals
- Next by Date: Re: UDF filesystem has some bugs on truncating
- Previous by thread: Re: [git pull] ieee1394 tree for 2.6.18
- Next by thread: Re: [git pull] ieee1394 tree for 2.6.18
- Index(es):
Relevant Pages
|
