From: Vitor Antunes <vitor.hda@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org, David Barr <davidbarr@google.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [PATCH v0] fast-import: Add drop command
Date: Sat, 24 Sep 2011 22:35:26 +0100 [thread overview]
Message-ID: <20110924223526.02ca9edf@fenix.utopia.dhis.org> (raw)
In-Reply-To: <20110924193733.GB10955@elie>
On Sep 24, 2011 8:37 PM, "Jonathan Nieder" <jrnieder@gmail.com> wrote:
> Thanks. I must have missed the earlier discussion. What are the
> semantics of this command and its intended purpose? For example, what
> happens if the branch already existed or if there is a checkpoint
> (perhaps triggered by the impatient user sending SIGUSR1 to
> fast-import) before the "drop" command is processed?
In the tests I made there are checkpoints triggered before using the
command. I tried to remove the branch within fast-import variables as well
as the already processed objects in git.
This command is required because I need to reset a given branch multiple
times in order to be able to "guess" its origin commit in the parent branch.
To make this analysis I also need to use "checkpoint" at each try.
(Resending... apparently gmail Android app sends a HTML attachment)
prev parent reply other threads:[~2011-09-24 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 15:27 [PATCH v0] fast-import: Add drop command Vitor Antunes
2011-09-24 15:27 ` Vitor Antunes
2011-09-24 19:37 ` Jonathan Nieder
2011-09-24 21:19 ` Dmitry Ivankov
2011-09-27 8:57 ` Vitor Antunes
2011-10-24 16:37 ` Vitor Antunes
2011-10-24 18:01 ` Sverre Rabbelier
2011-10-25 9:56 ` Vitor Antunes
2011-10-27 11:06 ` Sverre Rabbelier
2011-10-27 11:22 ` Vitor Antunes
2011-10-27 14:36 ` Sverre Rabbelier
2011-11-09 0:24 ` Vitor Antunes
2011-11-09 0:27 ` Sverre Rabbelier
2011-11-09 11:29 ` Vitor Antunes
2011-09-24 21:35 ` Vitor Antunes [this message]
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=20110924223526.02ca9edf@fenix.utopia.dhis.org \
--to=vitor.hda@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=srabbelier@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).