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.