From: Vitor Antunes <vitor.hda@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Dmitry Ivankov <divanorama@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, David Barr <davidbarr@google.com>
Subject: Re: [PATCH v0] fast-import: Add drop command
Date: Thu, 27 Oct 2011 12:22:08 +0100 [thread overview]
Message-ID: <CAOpHH-W30umoP6CuvrXgiSPBC2NjLvNWUX0uxhU4SU3kBB4H-A@mail.gmail.com> (raw)
In-Reply-To: <CAGdFq_iY92Gc=WLFVVMpi8w5JNZMo5bSk5=wjHyCmjXmP4RXrQ@mail.gmail.com>
On Thu, Oct 27, 2011 at 12:06 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> I'm afraid I don't understand why it's a bad thing that fast-import
> will find the old tree on disk, won't it just be gc-ed if it is no
> longer used?
No, because fast-import actively checks this to make sure the frontend
script did not do anything wrong during the import. I think the check
makes sense and may help debugging a corner case the frontend script
does not support. So, using "--force" is also not a solution because it
ignores everything and not only the specific commits I want to leave
behind.
Vitor
next prev parent reply other threads:[~2011-10-27 11:22 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 [this message]
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
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=CAOpHH-W30umoP6CuvrXgiSPBC2NjLvNWUX0uxhU4SU3kBB4H-A@mail.gmail.com \
--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).