Re: How to manage heads on a remote repository?

From: Theodore Tso <tytso@mit.edu>
Date: Oct 14, 2007, 11:32 UTC
Message-ID: <20071014113206.GB17368@thunk.org>
In-Reply-To: <ee77f5c20710140412s1eb68991ke552995dbbd226b@mail.gmail.com>

On Sun, Oct 14, 2007 at 09:12:43PM +1000, David Symonds wrote:

Show 11 quoted lines

> On 14/10/2007, Theodore Tso <tytso@mit.edu> wrote:
> > On Sun, Oct 14, 2007 at 09:03:48PM +1000, David Symonds wrote:
> > > 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.
> 
> Yes, it is, including in the examples section.

Wow, I completely missed that!  It would be nice if:

       <refspec>
          The canonical format of a <refspec> parameter is +?<src>:<dst>; that
          is, an optional plus +, followed by the source ref, followed by a
          colon :, followed by the destination ref.

.... mentioned that the source ref could be optional (just like it explicitly says the '+' is optional)...

          The <src> side can be an arbitrary "SHA1 expression" that can be
          used as an argument to git-cat-file -t. E.g. master~4 (push four
          parents before the current master head).

.... and I think the throwaway sentence at the end of the refspec would be better at the end of the second paragraph above. I'll send a patch.

Thanks for pointing that out!

       	      	     	 		  - Ted