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

Re: [PATCH 2/2] fetch: handle overlaping refspecs on --prune

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 28, 2014, 18:04 UTC
Message-ID
<xmqqy50vun9r.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1393590104.5277.19.camel@centaur.cmartin.tk>
Carlos Martín Nieto <cmn@elego.de> writes:
Show 5 quoted lines
> ... However, we now
> have 'origin/master' and 'origin/pr/5' both of which match the
> 'refs/remotes/origin/*' pattern. The current behaviour is to stop at the
> first match, which would mark it as stale as there is no
> 'refs/heads/pr/5' branch in the remote.

OK, but with a later pattern, we can find out that it came from pull/5 that was advertised by the remote. If we had origin/pr/1 when the remote no longer has pull/1, then we can say that is stale.

Makes sense.  Thanks for an explanation.

I wonder how well --prune would work on a repository in pre 1.5 layout, where all branches were copied to local refs/heads/ hierarchy except for 'master' (which is renamed to 'origin'). Does it have a similar issue? Do we end up pruning refs/heads/origin away because we do not see it on the remote end, or we somehow already deal with it and not have to worry about it?

Previous: Carlos Martín NietoNext: Junio C Hamano
Message 8 of 11 in “fetch: add a failing test for prunning with overlapping refspecs”
  1. 1/2 fetch: add a failing test for prunning with overlapping refspecsCarlos Martín Nieto, Feb 27, 2014
  2. 2/2 fetch: handle overlaping refspecs on --pruneCarlos Martín Nieto, Feb 27, 2014
  3. Michael HaggertyFeb 27, 2014
  4. Carlos Martín NietoFeb 27, 2014
  5. Junio C HamanoFeb 27, 2014
  6. Junio C HamanoFeb 27, 2014
  7. Carlos Martín NietoFeb 28, 2014
  8. Junio C HamanoFeb 28, 2014
  9. Junio C HamanoMar 24, 2014
  10. Eric SunshineFeb 27, 2014
  11. Eric SunshineFeb 27, 2014

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.