Git development
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git am from scratch
Date: Thu, 19 Mar 2009 21:42:49 +0100	[thread overview]
Message-ID: <200903192142.49754.agruen@suse.de> (raw)
In-Reply-To: <20090319201817.GE17028@coredump.intra.peff.net>

On Thursday, 19 March 2009 21:18:17 Jeff King wrote:
> I don't think this has ever worked in any version of git.

I did find a way to help myself in the end. Still it was still a major, 
unnecessary annoyance.

I ran into this problem when trying to reconstruct a project's history (after 
going RCS -> CVS -> git many things were still wrong like unrelated RCS files 
which ended up in the history, RCS files being moved to the Attic in the 
original tree to indicate deletes [which means they will happily live on from 
a CVS point of view], etc.).

The easiest way I could find how to get rid of all the mess without going 
totally insane was to git-format-patch the repository, fix up the major 
things in the mbox, and then recreate the history.

In the end I ended up preparing the initial commit by hand followed 
by "commit -c HASH" to preserve the metadata. (The cvsimport branch had a 
different commit at its tip, so I couldn't use commit --amend on that.) After 
that, I git-am'ed the rest of the mbox onto that reconstructed commit. This 
could have been significantly easier.

> There are many other ways to do this.

That's really not the point. Thanks though.

Andreas

  reply	other threads:[~2009-03-19 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 15:09 git am from scratch Andreas Gruenbacher
2009-03-19 16:16 ` Eric Raible
2009-03-19 20:18 ` Jeff King
2009-03-19 20:42   ` Andreas Gruenbacher [this message]
2009-03-19 21:02     ` Jeff King
2009-03-19 21:57       ` Junio C Hamano
2009-03-20  1:06       ` Andreas Gruenbacher
2009-03-20  4:39         ` Jeff King

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=200903192142.49754.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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