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: Re: Branch deletion (Re: [RFC] fast-import: note deletion command)
Date: Sun, 18 Sep 2011 16:49:54 -0500 [thread overview]
Message-ID: <20110918214954.GL2308@elie> (raw)
In-Reply-To: <CAGdFq_gH=u1BU6k3Z23Lo9mOSE4Rq-6nWU0EE91CQNpxksGw5w@mail.gmail.com>
Sverre Rabbelier wrote:
> The problem currently is that when
> you try to "git push origin :experimental-branch", there is no way for
> the transport-helper code to tell the helper to delete the ref.
Ah! Thanks for explaining.
It also occurs to me that
reset refs/heads/experimental-branch
... rest of the fast-import stream comes here ...
could be used as an especially non-self-explanatory way to express
this kind of thing. :) No idea whether that works already. A
deleteref command and deleteref feature documented to be meant for
this purpose sound handy to me.
By the way, what does the "export" command do in the following
situation?
git push origin something-big:master
Does it assume the remote-tracking branch for master reflects what's
available on the other end and send a stream for
origin/master..something-big, or does it send the entire history of
something-big?
next prev parent reply other threads:[~2011-09-18 21:50 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 ` Branch deletion " Jonathan Nieder
2011-09-18 21:38 ` Sverre Rabbelier
2011-09-18 21:49 ` Jonathan Nieder [this message]
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=20110918214954.GL2308@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).