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

Re: [PATCHv3 1/4] parse-remote: function to get the tracking branch to be merge

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 8, 2009, 23:30 UTC
Message-ID
<7v8wk2wbfs.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1244451651-22651-2-git-send-email-santi@agolina.net>
Santi Béjar <santi@agolina.net> writes:
Show 5 quoted lines
> The only user of get_remote_refs_for_fetch was "git pull --rebase" and
> it only wanted the tracking branch to be merge. So, add a simple
> function with this new meaning.
>
> No behavior changes.

I am all for code reduction, but after following the original logic that uses remote_refs_for_fetch (which knows about things like "git pull there +refs/heads/master:refs/heads/origin tag v1.6.0" from the command line) that in turn calls canon_refs_list_for_fetch (which returns a list e.g. +refs/heads/master:refs/heads/origin refs/tags/v1.6.0:refs/tags/v1.6.0), and do not quite see how you can casually say "No behaviour changes."

Previous: Santi BéjarNext: Santi Béjar
Message 2 of 8 in “[PATCHv3 1/4] parse-remote: function to get the tracking branch to be merge”
  1. Santi BéjarJun 8, 2009
  2. Junio C HamanoJun 8, 2009
  3. Santi BéjarJun 9, 2009
  4. Santi BéjarJun 9, 2009
  5. Junio C HamanoJun 9, 2009
  6. Santi BéjarJun 9, 2009
  7. Santi BéjarJun 9, 2009
  8. Santi BéjarJun 11, 2009

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.