From: Petr Baudis <pasky@suse.cz>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Brian Foster <brian.foster@innova-card.com>, git@vger.kernel.org
Subject: Re: Re: Re: fsck --full is Ok, but clones are not, "missing commits"?!
Date: Wed, 16 Apr 2008 16:59:00 +0200 [thread overview]
Message-ID: <20080416145900.GA10777@machine.or.cz> (raw)
In-Reply-To: <20080416121424.GA3133@dpotapov.dyndns.org>
On Wed, Apr 16, 2008 at 04:14:24PM +0400, Dmitry Potapov wrote:
> info/grafts should never be used during normal work.
I don't really agree with this advice in general. Grafts can be very
useful especially when migrating to Git - a very good strategy might be
just to start from scratch with your current state, then import your
previous history and graft it. The big advantage is that if you find out
later that the import is screwed up, you can fix that and reimport. The
fact that you don't need to haul 10 years of CVS history around unless
you actually know you need it can be perceived as both advantage and
disadvantage.
The _BAD_ grafts are those that replace list of commit's parents instead
of just appending (typically to an empty one). I didn't actually have
any idea people use grafts in such a twisted and perverse way... ;-)
--
Petr "Pasky" Baudis
Whatever you can do, or dream you can, begin it.
Boldness has genius, power, and magic in it. -- J. W. von Goethe
next prev parent reply other threads:[~2008-04-16 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804161334.17748.brian.foster@innova-card.com>
2008-04-16 11:48 ` Re: Re: fsck --full is Ok, but clones are not, "missing commits"?! Brian Foster
2008-04-16 12:14 ` Dmitry Potapov
2008-04-16 14:59 ` Petr Baudis [this message]
2008-04-16 16:23 ` Dmitry Potapov
2008-04-16 13:22 ` Johannes Sixt
2008-04-16 14:25 ` Dmitry Potapov
2008-04-16 14:56 ` Johannes Sixt
2008-04-16 16:17 ` Dmitry Potapov
2008-04-16 16:47 ` Jakub Narebski
2008-04-17 6:18 ` Johannes Sixt
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=20080416145900.GA10777@machine.or.cz \
--to=pasky@suse.cz \
--cc=brian.foster@innova-card.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).