From: Eugene Sajine <euguess@gmail.com>
Date: Mon, 28 Jun 2010 17:43:22 GMT
Subject: Re: origin/branchname and tracking branch pointing to different commits?
Message-ID: <AANLkTik7bleuzqnMWMJoWljQ5zD0YbwBsFjZT5IzkV0q@mail.gmail.com>
In-Reply-To: <20100608183007.GA31293@coredump.intra.peff.net>

On Tue, Jun 8, 2010 at 2:30 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Jun 08, 2010 at 12:27:14PM -0400, Eugene Sajine wrote:
>
>> I'm coming back to this topic as i see some confusion growing about
>> such behavior. Every now and then users come across this problem and
>> they expect pull to *really* behave as fetch and merge so it will
>> cause the update of remote/branchname branch. And it is kind of
>> difficult to justify why they have to do git fetch after pull...
>>
>> Can somebody, please, take a look?
>
> This was discussed a while back:
>
>  http://thread.gmane.org/gmane.comp.version-control.git/127163
>
> and I even posted a patch, but never followed up (I think mostly just
> due to being busy).. There is some concern about unexpected ref updates,
> though.
>
> -Peff
>

Jeff, Junio

Could you, please, advise if there is any resolution on the patch?

Thanks a lot,
Eugene