Carl Worth [off-list ref] writes:
Is there any plan to make git-clone take advantage of this capability
so that one can track an upstream that has branches that get
added/remove without having to learn how to manually maintain the
current list of branches in .git/config ?
Could you check "log master..next" and see if you like what has
been cooking, please?
The next batch of 'master' updates will have jc/clone topic (see
the latest issue of "What's cooking" message on the list) which
will include what has been cooking in 'next' around this area.
On Wed, 20 Dec 2006 14:36:12 -0800, Junio C Hamano wrote:
Carl Worth [off-list ref] writes:
quoted
Is there any plan to make git-clone take advantage of this capability
so that one can track an upstream that has branches that get
added/remove without having to learn how to manually maintain the
current list of branches in .git/config ?
Could you check "log master..next" and see if you like what has
been cooking, please?
Oh, yes, there it is. (I had skimmed the log for master..next but had
missed it---I guess that I also searched for "glob" instead of
"wildcard" didn't help).
Anyway, yes, the description of the new stuff there looks very
interesting, and I'll maybe I'll start running from next a bit to see
how this stuff all works.
I guess the big reason I wrote was that I was surprised to see your
reply instructing Sean on how to update the config file without also
saying something like, "by the way, this need to update the config
file like this will be going away with new work on git-clone that is
being done now and is expected to be in the upcoming git 1.5".
I thought that was the case, but didn't want to say it without
confirming it first. Thanks for confirming it for me.
-Carl