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

Re: Malformed branch name in fast-export when specifying non-HEAD/branch revision

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 22, 2011, 21:27 UTC
Message-ID
<7vpqjxuogr.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110822175705.GB1945@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Yeah, the behavior of your patch looks fine to me. I thought the point
> in contention was that having export understand refspecs would fix a lot
> of _other_ cases, too.

Perhaps if we added refspecs we could cover other cases, too, but I do not think we need to require the patch to cover additional cases. The more problematic was that the particular implementation in the patch smelled bad.

Previous: Sverre RabbelierNext: Jeff King
Message 10 of 11 in “Malformed branch name in fast-export when specifying non-HEAD/branch revision”
  1. Owen StephensAug 17, 2011
  2. Elijah NewrenAug 17, 2011
  3. Junio C HamanoAug 17, 2011
  4. Jeff KingAug 17, 2011
  5. Sverre RabbelierAug 21, 2011
  6. Jeff KingAug 22, 2011
  7. Sverre RabbelierAug 22, 2011
  8. Jeff KingAug 22, 2011
  9. Sverre RabbelierAug 22, 2011
  10. Junio C HamanoAug 22, 2011
  11. Jeff KingAug 22, 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.