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

Re: [PATCH] Fix push with refspecs containing wildcards

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 8, 2007, 06:38 UTC
Message-ID
<7v4pljlzm3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070607234305.GB10633@steel.home>

Sending a fix is a good thing, but whenever doing one, could people please also do a testcase that demonstrates the original bug, and also a demonstration that the fix does not introduce regression?

For this one, obviously a test for push that uses such wildcard ref is needed but at the same time we would want a test for push that does _not_ use a wildcard, fetch that uses a wildcard, and a fetch that does not use a wildcard.

Previous: Alex RiesenNext: Junio C Hamano
Message 6 of 8 in “git-send-pack: broken handling of ref specs with wildcards”
  1. Alex RiesenJun 7, 2007
  2. Johannes SchindelinJun 7, 2007
  3. Junio C HamanoJun 8, 2007
  4. Daniel BarkalowJun 8, 2007
  5. Fix push with refspecs containing wildcardsAlex Riesen, Jun 7, 2007
  6. Junio C HamanoJun 8, 2007
  7. Junio C HamanoJun 8, 2007
  8. Alex RiesenJun 8, 2007

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.