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

Re: [PATCH v2 2/2] receive-pack: detect aliased updates which can occur with symrefs

From
Jay Soffian <jaysoffian@gmail.com>
Date
Apr 19, 2010, 16:31 UTC
Message-ID
<v2r76718491004190931rb9813deex2797a440d09b50a5@mail.gmail.com>
In-Reply-To
<1271694343-31876-2-git-send-email-jaysoffian@gmail.com>
On Mon, Apr 19, 2010 at 12:25 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
> When pushing to a remote repo the sending side filters out aliased
> updates (e.g., foo:baz bar:baz). However, it is not possible for the
> sender to know if two refs are aliased on the receiving side via
> symrefs. Here is one such scenario:
Don't receive this. There's a logic error in it. I'll send a follow up shortly.
j.
Previous: Jay SoffianNext: Jay Soffian
Message 3 of 17 in “receive-pack: switch global variable 'commands' to a parameter”
  1. 1/2 receive-pack: switch global variable 'commands' to a parameterJay Soffian, Apr 19, 2010
  2. 2/2 receive-pack: detect aliased updates which can occur with symrefsJay Soffian, Apr 19, 2010
  3. Jay SoffianApr 19, 2010
  4. 2/2 receive-pack: detect aliased updates which can occur with symrefsJay Soffian, Apr 19, 2010
  5. Junio C HamanoApr 19, 2010
  6. Jay SoffianApr 19, 2010
  7. 0/3 js/maint-receive-pack-symref-aliasJay Soffian, Apr 19, 2010
  8. 1/3 receive-pack: switch global variable 'commands' to a parameterJay Soffian, Apr 19, 2010
  9. 2/3 t5516-fetch-push.sh: style cleanupJay Soffian, Apr 19, 2010
  10. 3/3 receive-pack: detect aliased updates which can occur with symrefsJay Soffian, Apr 19, 2010
  11. ignoring a fetch that overwrites local symrefJunio C Hamano, Dec 11, 2012
  12. fetch: ignore wildcarded refspecs that update local symbolic refsJunio C Hamano, Dec 11, 2012
  13. Jay SoffianDec 12, 2012
  14. Shawn PearceDec 12, 2012
  15. Junio C HamanoDec 12, 2012
  16. 3/3 receive-pack: detect aliased updates which can occur with symrefsJay Soffian, Apr 19, 2010
  17. Ævar Arnfjörð BjarmasonJun 10, 2010

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.