From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jonathan Nieder <jrnieder@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: Re: [RFC] fast-import: note deletion command
Date: Sun, 18 Sep 2011 22:39:40 +0200 [thread overview]
Message-ID: <CAGdFq_hpA95Kj4eMr4e1duuXTpr+OkkwF4K5bTapXEi9UjWcSA@mail.gmail.com> (raw)
In-Reply-To: <20110918203506.GG2308@elie>
Heya,
On Sun, Sep 18, 2011 at 22:35, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> ND commit_sha1 # One may think there are also NC, NR, NM
>> N delete commit_sha1
>> # Only :mark, full-40-byte-sha1 and 'inline' are allowed currently.
>> # So no clashes arise, but then one may also want M 'delete' path
>> # command to work too.
>
> If I were doing it:
>
> - advertise "N 0{40} <commit>" as the historical way to delete a
> note, and make sure it keeps working
>
> - introduce 'ND' or 'notedelete <commit>' as a human-friendly
> synonym, keeping in mind that NC and NR could be introduced in the
> future if there is demand for them.
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.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-09-18 20:40 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 [this message]
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 ` Branch deletion " Jonathan Nieder
2011-09-18 21:38 ` 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=CAGdFq_hpA95Kj4eMr4e1duuXTpr+OkkwF4K5bTapXEi9UjWcSA@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.org \
--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).