list mirror (unofficial, one of many)
 help / color / Atom feed
From: Derrick Stolee <>
To: "Uwe Brauer" <>, "SZEDER Gábor" <>
Cc: git <>
Subject: Re: I just pulled, and git log --graph does not show all
Date: Wed, 9 Oct 2019 08:33:22 -0400
Message-ID: <> (raw)
In-Reply-To: <>

On 10/9/2019 2:13 AM, Uwe Brauer wrote:
>    > On Tue, Sep 24, 2019 at 12:22:27PM +0200, Uwe Brauer wrote:
>    > I hear you: I had a brief encounter with Mercurial not that long ago, 
>    > and there were several things that didn't work the way I expected (or 
>    > rather: the way I got used to with Git).  The subtle and sometimes
>    > not-so-subtle differences between the concepts and philosophy of the
>    > two systems might very well explain why Git didn't work the way you
>    > expected.
>    > However, it's impossible to give any explanation or advice without
>    > knowing more about the situation, e.g. at least the exact commands
>    > that you run and what they outputted, if you still have them or at
>    > least if you can still reproduce the issue. (with potentially
>    > sensitive URLs and/or branchnames redacted, if necessary).
> Thanks for your answer.
> Could you please try out 
> git clone matlab-emacs-hg
> Then you will see
> That 
> git log --graph
> and
> git log --graph --all
> Are giving two different results and I don't understand why the branch
> is not shown when using 
> git log --graph
> Funny thing is when I use the hg-git plugin and run 
> hg clone matlab-emacs-hg
> I see this branch, converted to a hg bookmark.

"git log --graph" has an implicit "HEAD" added on the end, to say
"start walking from my current commit". The "--all" says "walk from
all refs", so the set of commits to walk is larger.

"git log" defaults to showing history from your current position in
history, so you can look at the recent commits that you have created
or what changes led to your current state. Adding the "--all" gives
you a higher-level view of the repository, but can be very noisy
when trying to discover what has happened for your current state.

In particular, say you are trying to dig into a bug in Git 2.23.0.
A "git checkout v2.23.0" will change your HEAD to be at the commit
used to build that version. You can use "git log" to view the
history leading to that release, and see if you can determine recent
changes that would have caused a regression. If you use "git log --all",
then the commits in the "master" branch will appear before your
current HEAD, and you'll be looking at commits that "haven't happened
yet" according to your current place in history.

I hope this helps.


  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 10:22 Uwe Brauer
2019-10-08 23:01 ` SZEDER Gábor
2019-10-09  6:13   ` Uwe Brauer
2019-10-09 12:33     ` Derrick Stolee [this message]
2019-10-09 13:23     ` SZEDER Gábor
2019-10-09 13:36       ` Uwe Brauer
2019-10-09 14:06       ` Uwe Brauer

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone