Re: [PATCH] Clarified how "git submodule add" handles relative paths.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 3, 2011, 23:16 UTC
- Message-ID
- <7vhb86a4kt.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <4DE93B29.4030401@web.de>
Jens Lehmann <Jens.Lehmann@web.de> writes:
Show 5 quoted lines
> Now I understand this issue better I'd vote for leaving the relative url > like it is, comment it better in the man page and give a better error > message when that happens. After all this issue only surprised a few > people, mostly due to the lack of information in the error message and > man page, so I'd rather prefer to not change the behavior but the wording.
The "how about this" patch you are voting against (I am neutral by the way) is a response to your earlier "I have three use cases and the current implementation is forgetting the third", which in turn was a response to my "your third use case does not count, so the updated wording of the documentation is wrong---it should say 'do not', not 'cannot'".
So what should the updated document say?