git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Dmitry Ivankov <divanorama@gmail.com>,
	Git List <git@vger.kernel.org>, David Barr <davidbarr@google.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Thomas Rast <trast@student.ethz.ch>,
	Johan Herland <johan@herland.net>
Subject: Branch deletion (Re: [RFC] fast-import: note deletion command)
Date: Sun, 18 Sep 2011 16:18:36 -0500	[thread overview]
Message-ID: <20110918211836.GI2308@elie> (raw)
In-Reply-To: <CAGdFq_hpA95Kj4eMr4e1duuXTpr+OkkwF4K5bTapXEi9UjWcSA@mail.gmail.com>

Sverre Rabbelier wrote:

> Is this perhaps a good moment to also think about branch deletion?
> That came up earlier as well, and thinking about that might give us
> some insights in how to deal with deletions uniformly.

Sorry, my earlier reply missed the point.  To answer your question:
Dmitry's RFC was about deleting individual notes rather than entire
notes refs, so it is not too closely related to branch deletion.

A new "deleteref" command would be a very simple addition, and the UI
seems pretty obvious.  The main concern in adding such a thing is that
it destroys history, while currently "git fast-import" without -f does
not provide any commands that can do that.  So presumably one would
want to do one of the following:

 - only allow deletion of refs that were not present at the start of
   the import, or
 - add a command-line option to permit deletion of refs, so it doesn't
   happen by mistake when misparsing a stream.

It would also be interesting to see an example use (do you remember
the earlier thread where it came up?) to make sure the UI fits it
well.  In most typical cases I can imagine, direct use of "git
update-ref -d" would work better.  In the case of remote helpers, IIRC
there was already a need for the transport-helper to handle the final
ref updates so "git fetch" can write a nice notice about them to the
console.

  parent reply	other threads:[~2011-09-18 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 20:07 [RFC] fast-import: note deletion command Dmitry Ivankov
2011-09-18 20:35 ` Jonathan Nieder
2011-09-18 20:39   ` Sverre Rabbelier
2011-09-18 20:59     ` Dmitry Ivankov
2011-09-18 21:03       ` fast-import wishlist (Re: [RFC] fast-import: note deletion command) Jonathan Nieder
2011-09-18 21:18     ` Jonathan Nieder [this message]
2011-09-18 21:38       ` Branch deletion " Sverre Rabbelier
2011-09-18 21:49         ` Jonathan Nieder
2011-09-18 21:54           ` Dmitry Ivankov
2011-09-18 21:55           ` 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=20110918211836.GI2308@elie \
    --to=jrnieder@gmail.com \
    --cc=davidbarr@google.com \
    --cc=divanorama@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.net \
    --cc=spearce@spearce.org \
    --cc=srabbelier@gmail.com \
    --cc=trast@student.ethz.ch \
    /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).