Re: What's cooking in git.git (May 2009, #02; Sun, 17)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 19, 2009, 01:33 UTC
- Message-ID
- <7vpre5anaz.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <200905182355.21645.johan@herland.net>
Johan Herland <johan@herland.net> writes:
> After some thinking, I don't like my original name submodule.<name>.resolve, > since ".resolve" sounds more like a merge strategy or conflict resolution > method, than a "how to deal with submodule update" choice. I propose > submodule.<name>.update instead.
Sounds like a plan, even though I do not necessarily agree with the idea of automatically rebinding what is at the submodule path every time you update the toplevel project tree. And from my point of view, "rebind" (or "autorebind") would be more appropriate name than "update" (and I would probably set it to "never").