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

Re: [PATCH v6 5/8] branch: drop non-commit error reporting

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 23, 2015, 22:50 UTC
Message-ID
<xmqqeghowy1l.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<vpq6130ucbh.fsf@grenoble-inp.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 6 quoted lines
> To be sure, I tried:
>
>   echo ee0f5eeeae36cd1b5a346a1e2ae5c8cb841cd5da > .git/refs/heads/broken
>
> where the sha1 is the one of a blob.
> ...

After doing (something like) the above, running "git push --mirror" to various Git repositories shows their slightly different behaviour.

The most intriguing one was github.com:gitster/git.git repository.
To github.com:gitster/git.git
 ! [remote rejected] jk/transfer-limit-protocol -> jk/transfer-limit-protocol (failed)
 ! [remote rejected] ls/p4-lfs -> ls/p4-lfs (failed)
 ...
 ! [remote rejected] pu -> pu (failed)
 ! [remote rejected] broken -> broken (failed)
 ! [remote rejected] jc/fsck-dropped-errors -> jc/fsck-dropped-errors (failed)
 ! [remote rejected] kn/for-each-branch -> kn/for-each-branch (failed)

After removing the broken branch, retrying "git push --mirror github.com:gitster/git.git" was successful. I didn't dig further (it didn't reproduce with a pair of toy local repositories).

It is puzzling that it is behaving as if I am trying to perform an atomic push and rejection of "broken" is causing everything else to be rejected or something like that.

Perhaps GitHub has a pre-receive hook to reject such nonsense?
Previous: Matthieu MoyNext: Karthik Nayak
Message 15 of 27 in “port branch.c to use the filtering part of ref-filter.”
  1. 0/8 port branch.c to use the filtering part of ref-filter.Karthik Nayak, Sep 23, 2015
  2. 1/8 branch: refactor width computationKarthik Nayak, Sep 23, 2015
  3. 2/8 branch: bump get_head_description() to the topKarthik Nayak, Sep 23, 2015
  4. 3/8 branch: roll show_detached HEAD into regular ref_listKarthik Nayak, Sep 23, 2015
  5. 4/8 branch: move 'current' check down to the presentation layerKarthik Nayak, Sep 23, 2015
  6. 5/8 branch: drop non-commit error reportingKarthik Nayak, Sep 23, 2015
  7. Matthieu MoySep 23, 2015
  8. Karthik NayakSep 24, 2015
  9. Junio C HamanoSep 23, 2015
  10. Matthieu MoySep 23, 2015
  11. Junio C HamanoSep 23, 2015
  12. Junio C HamanoSep 23, 2015
  13. Junio C HamanoSep 23, 2015
  14. Matthieu MoySep 24, 2015
  15. Junio C HamanoSep 23, 2015
  16. Karthik NayakSep 24, 2015
  17. 6/8 branch.c: use 'ref-filter' data structuresKarthik Nayak, Sep 23, 2015
  18. 7/8 branch.c: use 'ref-filter' APIsKarthik Nayak, Sep 23, 2015
  19. 8/8 branch: add '--points-at' optionKarthik Nayak, Sep 23, 2015
  20. Matthieu MoySep 23, 2015
  21. Junio C HamanoSep 23, 2015
  22. Karthik NayakSep 24, 2015
  23. 5/8 branch: drop non-commit error reportingKarthik Nayak, Sep 24, 2015
  24. Matthieu MoySep 25, 2015
  25. Junio C HamanoSep 25, 2015
  26. Matthieu MoySep 25, 2015
  27. Karthik NayakSep 25, 2015

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.