From: Keith Packard <keithp@keithp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: keithp@keithp.com, Carl Worth <cworth@cworth.org>,
Nicolas Vilz 'niv' <niv@iaglans.de>, git <git@vger.kernel.org>
Subject: Re: several quick questions
Date: Tue, 14 Feb 2006 11:39:27 -0800 [thread overview]
Message-ID: <1139945967.4341.71.camel@evo.keithp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602141101110.3691@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Tue, 2006-02-14 at 11:04 -0800, Linus Torvalds wrote:
> Try doing that on a big project, and it will just kill you. You've also
> lost the "top-of-branch" info, but if you're just tracking some other
> tree, that's likely not an issue.
I was validating the cvs import by comparing every tagged version. Trust
me, the git tree-rewriting stage was somewhat faster than the CVS
checkout of the same content. And, as an egg, one often prefers BFI to
finesse. I had trouble figuring out precisely what sequence of commands
were needed to make git-reset --hard happy with existing bits in the
directory.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-14 19:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 16:28 several quick questions Nicolas Vilz 'niv'
2006-02-14 17:03 ` Andreas Ericsson
2006-02-14 21:30 ` Nicolas Vilz 'niv'
2006-02-14 17:05 ` Linus Torvalds
2006-02-14 17:47 ` Kenneth Johansson
2006-02-14 18:08 ` Andreas Ericsson
2006-02-14 18:21 ` Kenneth Johansson
2006-02-14 18:26 ` Linus Torvalds
2006-02-14 18:10 ` Carl Worth
2006-02-14 18:34 ` Linus Torvalds
2006-02-14 20:10 ` Carl Worth
2006-02-14 20:27 ` Petr Baudis
2006-02-14 20:37 ` Johannes Schindelin
2006-02-14 20:41 ` Junio C Hamano
2006-02-14 20:54 ` Johannes Schindelin
2006-02-14 20:55 ` Petr Baudis
2006-02-14 20:40 ` Linus Torvalds
2006-02-14 21:19 ` Petr Baudis
2006-02-14 21:53 ` Carl Worth
2006-02-14 22:39 ` Junio C Hamano
2006-02-23 20:31 ` [PATCH] New git-seek command with documentation and test Carl Worth
2006-02-24 0:18 ` J. Bruce Fields
2006-02-24 1:01 ` [PATCH] git-seek: Eliminate spurious warning. Fix errant reference to git-bisect in docs Carl Worth
2006-02-24 6:02 ` Junio C Hamano
2006-02-24 10:00 ` [PATCH] New git-seek command with documentation and test Andreas Ericsson
2006-02-24 11:38 ` Junio C Hamano
2006-02-24 14:23 ` Carl Worth
2006-02-24 21:48 ` Johannes Schindelin
2006-02-24 21:57 ` J. Bruce Fields
2006-02-14 21:30 ` several quick questions Josef Weidendorfer
2006-02-14 21:40 ` Junio C Hamano
2006-02-14 22:17 ` Josef Weidendorfer
2006-02-14 22:26 ` Junio C Hamano
2006-02-15 19:22 ` [PATCH] More useful/hinting error messages in git-checkout Josef Weidendorfer
2006-02-14 23:00 ` several quick questions Andreas Ericsson
2006-02-14 23:23 ` Johannes Schindelin
2006-02-15 0:08 ` Andreas Ericsson
2006-02-15 0:34 ` Junio C Hamano
2006-02-15 6:27 ` Junio C Hamano
2006-02-15 9:06 ` Andreas Ericsson
2006-02-15 9:21 ` Junio C Hamano
2006-02-14 21:41 ` Petr Baudis
2006-02-14 18:44 ` Carl Worth
2006-02-14 19:00 ` Linus Torvalds
2006-02-14 19:38 ` Andreas Ericsson
2006-02-14 20:34 ` Johannes Schindelin
2006-02-14 20:14 ` Carl Worth
2006-02-14 18:55 ` Keith Packard
2006-02-14 19:04 ` Linus Torvalds
2006-02-14 19:39 ` Keith Packard [this message]
[not found] ` <20060214220154.GJ31278@pasky.or.cz>
[not found] ` <1139960934.4341.93.camel@evo.keithp.com>
[not found] ` <20060215000737.GF9573@pasky.or.cz>
[not found] ` <1139963183.4341.117.camel@evo.keithp.com>
2006-02-15 1:12 ` Cogito turbo-introduction Petr Baudis
2006-02-15 1:32 ` Petr Baudis
2006-02-15 4:11 ` several quick questions Martin Langhoff
2006-02-15 5:25 ` Keith Packard
2006-02-15 8:21 ` Carl Worth
2006-02-14 19:13 ` Junio C Hamano
2006-02-14 19:46 ` Petr Baudis
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=1139945967.4341.71.camel@evo.keithp.com \
--to=keithp@keithp.com \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=niv@iaglans.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.