Re: How to manage heads on a remote repository?
- From
David Symonds <dsymonds@gmail.com>
- Date
- Oct 14, 2007, 11:03 UTC
- Message-ID
- <ee77f5c20710140403j7a88ffa4q579a8c4118d8fd71@mail.gmail.com>
- In-Reply-To
- <E1Ih0zJ-0004FZ-0A@tinytim.thunk.org>
On 14/10/2007, Theodore Ts'o <tytso@mit.edu> wrote:
Show 8 quoted lines
> > 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.
Dave.