From: Uwe Brauer <oub@mat.ucm.es>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, git <git@vger.kernel.org>
Subject: Re: I just pulled, and git log --graph does not show all
Date: Wed, 09 Oct 2019 09:13:56 +0300 [thread overview]
Message-ID: <871rvmsaxn.fsf@mat.ucm.es> (raw)
In-Reply-To: 20191008230130.GE29845@szeder.dev
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
> 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 https://git.code.sf.net/p/matlab-emacs/src 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 https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-hg
I see this branch, converted to a hg bookmark.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-10-09 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 10:22 I just pulled, and git log --graph does not show all Uwe Brauer
2019-10-08 23:01 ` SZEDER Gábor
2019-10-09 6:13 ` Uwe Brauer [this message]
2019-10-09 12:33 ` Derrick Stolee
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rvmsaxn.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=git@vger.kernel.org \
--cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).