From: Jakub Narebski <jnareb@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Vitaliy Semochkin <vitaliy.se@gmail.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: Re: history missing
Date: Mon, 08 Nov 2010 05:29:20 -0800 (PST) [thread overview]
Message-ID: <m3mxpkeyh4.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=rT0S1H8pFt9d+FYVme4fjNNzY6O6evuBwo-ZB@mail.gmail.com>
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> writes:
> On Mon, Nov 8, 2010 at 4:02 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Vitaliy Semochkin wrote:
>>
>>> I cloned a remote repository
>>> to check recent changes in origin/master I do:
>>> git fetch origin master
This fetches into FETCH_HEAD _only_ from "origin" *remote*.
>>> git log origin master
This show log of 'origin/HEAD', which probably is 'origin/master'...
but which didn't get updated, and local branch 'master'.
>>>
>>> recently I found out that log doesn't show recent commits
>>
>> Yes, this can be confusing.
>
> I agree and I believe this has come up a lot of times before. I talked
> to Jeff and Junio about this at GitTogether and Jeff said he has a patch
> for it that he would try to get up to date in a while. (Thanks, Jeff!)
How can this issue be solved? The meaning of parameters in 'git fetch'
is different from meaning of parameters in 'git log'.
Unless it is about adding hint / advice for when doing
'git fetch <remote> <branch>'...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-11-08 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 19:47 history missing Vitaliy Semochkin
2010-10-26 20:04 ` Sverre Rabbelier
2010-11-08 9:02 ` Jonathan Nieder
2010-11-08 11:56 ` Martin von Zweigbergk
2010-11-08 13:29 ` Jakub Narebski [this message]
2010-11-08 13:37 ` Martin von Zweigbergk
2010-11-08 13:48 ` Jakub Narebski
2010-11-08 14:14 ` Martin von Zweigbergk
2010-11-08 18:28 ` Jeff King
2010-11-08 11:29 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mxpkeyh4.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=martin.von.zweigbergk@gmail.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
--cc=vitaliy.se@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).