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

Re: deleting non-existent ref via push

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Sep 24, 2011, 03:11 UTC
Message-ID
<CAMK1S_jjr5Lr1_N1aeTxRiaebdxu5b6Y6LiryMSq6NmfArc=0g@mail.gmail.com>
In-Reply-To
<7vmxdvunto.fsf@alter.siamese.dyndns.org>
On Fri, Sep 23, 2011 at 11:46 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 14 quoted lines
> Sitaram Chamarty <sitaramc@gmail.com> writes:
>
>> Pushing to delete a non-existent ref (git push origin :refs/heads/foo)
>> works without error, except for a warning that the remote is "Allowing
>> deletion of corrupt ref".  By "works" I mean all hooks are also
>> executed.
>>
>> Is this expected/supported behaviour?  Can I rely on it continuing to
>> work, especially in terms of executing hooks.
>
> This most definitely is just "we didn't bother checking the error too
> carefully, especially because the result of deleting something that did
> not exist in the first place is a no-op; anybody who tries to delete a
> non-existing thing is a moron and deserves whatever random result he

I'd better hide behind the fact that I am only doing it for the side-effect then ;-)

> gets".
>
> It would be a good idea to tighten it.
Thanks.  I just needed to know if I could rely on it long-term or not.
 I'll find some other way to "poke" a remote repo to run the hooks.
Previous: Junio C Hamano
Message 3 of 3 in “deleting non-existent ref via push”
  1. Sitaram ChamartySep 23, 2011
  2. Junio C HamanoSep 23, 2011
  3. Sitaram ChamartySep 24, 2011

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.