git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: David Symonds <dsymonds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to manage heads on a remote repository?
Date: Sun, 14 Oct 2007 07:07:14 -0400	[thread overview]
Message-ID: <20071014110714.GA17368@thunk.org> (raw)
In-Reply-To: <ee77f5c20710140403j7a88ffa4q579a8c4118d8fd71@mail.gmail.com>

On Sun, Oct 14, 2007 at 09:03:48PM +1000, David Symonds wrote:
> On 14/10/2007, Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > I'm currently exploring the idea of not only making the equivalent of
> > "pu" and "next" available on a public repository for one of my projects,
> > but also the topics/* branches.   When thinking about how I might do
> > this, one snag I ran into is that the topics/foo and topics/bar branches
> > are ephemeral, and so when I replicate them to a remote repository,
> > either on kernel.org or repo.or.cz, I would need a way of removing a
> > head for a topic branch that had already been merged.
> 
> git push <remote> :<branch_name>
> 
> If the left side of the colon in a push refspec is empty, it deletes
> the remote ref given by the right hand side.

Cool, thanks!  It's not in the git-push man page.  I'll play with it
some and then submit a patch update the man page.

     	      	       	     	    	    - Ted

  reply	other threads:[~2007-10-14 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 10:46 How to manage heads on a remote repository? Theodore Ts'o
2007-10-14 10:55 ` Michael Witten
2007-10-14 11:03 ` David Symonds
2007-10-14 11:07   ` Theodore Tso [this message]
2007-10-14 11:12     ` David Symonds
2007-10-14 11:32       ` Theodore Tso

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=20071014110714.GA17368@thunk.org \
    --to=tytso@mit.edu \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    /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).