From: Jonathan Nieder <jrnieder@gmail.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org, David Barr <davidbarr@google.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: git fast-import : How to change parent during import?
Date: Sun, 28 Aug 2011 18:39:32 -0500 [thread overview]
Message-ID: <20110828233931.GD29351@elie.gateway.2wire.net> (raw)
In-Reply-To: <20110828162325.5f479ef7@fenix.utopia.dhis.org>
Vitor Antunes wrote:
> Is there a way to manually force fast-import to drop an old commit that the
> frontend script decided it was no longer necessary?
Sure --- patch fast-import (I'd be happy to review such a patch). :)
next prev parent reply other threads:[~2011-08-28 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 1:21 git fast-import : How to change parent during import? Vitor Antunes
2011-03-08 2:44 ` Jonathan Nieder
2011-03-08 21:19 ` Vitor Antunes
2011-03-08 22:23 ` Jonathan Nieder
2011-03-09 14:21 ` Vitor Antunes
2011-03-30 17:25 ` Vitor Antunes
2011-08-28 15:23 ` Vitor Antunes
2011-08-28 23:39 ` Jonathan Nieder [this message]
2011-08-29 1:13 ` Sverre Rabbelier
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=20110828233931.GD29351@elie.gateway.2wire.net \
--to=jrnieder@gmail.com \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
--cc=vitor.hda@gmail.com \
/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).