--- Junio C Hamano <junkio@xxxxxxx> wrote:
> Junio C Hamano <junkio@xxxxxxx> writes:
>
> > Luben Tuikov <ltuikov@xxxxxxxxx> writes:
> >
> >> I can see that the remote heads are where they are supposed to be
> >> but no local tracking heads are created (by default). I had
> >> to do this manually.
> >>
> >> Old behavior was that git did that for you automatically.
> >> So I suppose this is another newbie protection.
> >
> > A very fuzzily stated question which is hard to answer, but I do
> > not think it is another newbie protection, if it apparently is
> > actively hurting you. Also the documentation may need to be
> > updated to teach you enough about how to achieve what you want.
>
> Can you state the problem you observed about the recent git in a
> way that is easier to debug?
>
> For example, you could state:
>
> With older git (I verified that v1.3.0 still works like
> this), I used to be able to just say:
>
> $ git fetch
>
> (this is the exact command line -- I am not giving a URL
> nor even "origin" after "git fetch"). When the upstream
> created a new branch 'blah', the above command created a
> new local branch 'blah' automatically for me. With the
> tip of 'master' (e27e609), this does not happen anymore.
>
> My configuration is that I have .git/remotes/origin file
> whose contents is .... I do not have any remote.*.url,
> remote.*.fetch, nor branch.*.remote configuration variables.
>
> to be more helpful.
>
> I am not dismissing your message as whining. You probably have
> hit a regression while we adopted the BCP to encourage separate
> remote layout, and I would like to understand the issue.
And I'm not whining. It just that when I've done something 1000
times and all of a sudden I do the same thing and didn't see the
expected behaviour, I posted.
"git-pull" didn't "create" the branches in the place I was
expecting. I.e. while they are in .git/refs/remotes/origin/
they are not in .git/refs/heads.
Then I manually created the heads in .git/refs/heads
and manually added that to .git/config, i.e. the [branch]
part.
I was hoping I wouldn't need to do that at all, as old
git-pull exposed remote branches, or I was expecting to
at least find a git command to do this 2nd additional
manual step for me.
Luben
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html