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

Re: [PATCH] Fix handling of not_for_merge '.' flag in refspec.

From
Junio C Hamano <junkio@cox.net>
Date
Sep 30, 2005, 00:47 UTC
Message-ID
<7vk6gzcrf8.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<11280379894186-git-send-email-tom.prince@ualberta.net>
Tom Prince <tom.prince@ualberta.net> writes:
> canon_refs_list_for_fetch did not know about '.', so it mangled any
> reference with it. Further, it added '.' to any refspec on the command
> line other than the first.

The dot trick was supposed to be internal. If you have the following three lines in a remotes/xyzzy file:

	URL: http://xyzzy.xz/balances.git
        Pull: frotz nitfol
        Pull: rezrov
    $ git pull xyzzy
    - fetch frotz, nitfol, and rezrov; merge frotz into the
      current branch
    $ git pull xyzzy nitfol
    - fetch nitfol only; merge nitfol into the current branch.
    $ git pull xyzzy nitfol rezrov
    - fetch nitfol and rezrov; merge them into the current
      branch (an Octopus).

The '.' is in no way part of the <refspec> format. It may not be a bad idea to explicitly forbid it, but currently we don't.

Previous: Tom Prince
Message 2 of 2 in “Fix handling of not_for_merge '.' flag in refspec.”
  1. Fix handling of not_for_merge '.' flag in refspec.Tom Prince, Sep 29, 2005
  2. Junio C HamanoSep 30, 2005

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.