git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to manage heads on a remote repository?

From
Theodore Tso <tytso@mit.edu>
Date
Oct 14, 2007, 11:07 UTC
Message-ID
<20071014110714.GA17368@thunk.org>
In-Reply-To
<ee77f5c20710140403j7a88ffa4q579a8c4118d8fd71@mail.gmail.com>
On Sun, Oct 14, 2007 at 09:03:48PM +1000, David Symonds wrote:
Show 14 quoted lines
> 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
Previous: David SymondsNext: David Symonds
Message 4 of 6 in “How to manage heads on a remote repository?”
  1. Theodore Ts'oOct 14, 2007
  2. Michael WittenOct 14, 2007
  3. David SymondsOct 14, 2007
  4. Theodore TsoOct 14, 2007
  5. David SymondsOct 14, 2007
  6. Theodore TsoOct 14, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.