git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Derrick Stolee <stolee@gmail.com>,
	Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Cc: vdye@github.com, Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Git List <git@vger.kernel.org>,
	kaartic.sivaraam@gmail.com
Subject: Re: [GSoC] Interest in "More Sparse Index Integrations" project idea
Date: Mon, 14 Feb 2022 13:45:16 -0500	[thread overview]
Message-ID: <e81f044d-8c3a-90df-ff9e-719b613807d6@gmail.com> (raw)
In-Reply-To: <d6286f84-642d-7448-0d2e-dd4c20bdb289@gmail.com>


> But of course, this doesn't show the full history of the work in
> each of these branches, so you can do a history walk from each
> merge to get a picture of the full series:
> 
> $ git log --oneline --graph 3c0e4178277 -6
> *   3c0e4178277 Merge branch 'ds/fetch-pull-with-sparse-index'
> |\  

Or even better (you do not have to guess the number of commits in 
each series):

git log --oneline --graph 3c0e4178277^-

(see [1]). Why that syntax seems to completely ignore '--graph',
though is beyond me!

Philippe.

[1] https://git-scm.com/docs/gitrevisions#Documentation/gitrevisions.txt-emltrevgt-ltngtemegemHEAD-HEAD-2em

  reply	other threads:[~2022-02-14 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 12:44 [GSoC] Interest in "More Sparse Index Integrations" project idea Shaoxuan Yuan
2022-02-14 14:38 ` Derrick Stolee
2022-02-14 18:45   ` Philippe Blain [this message]
2022-02-15  2:29     ` Shaoxuan Yuan
2022-02-16  3:01     ` Shaoxuan Yuan
2022-02-15  2:29   ` Shaoxuan Yuan

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=e81f044d-8c3a-90df-ff9e-719b613807d6@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=shaoxuan.yuan02@gmail.com \
    --cc=stolee@gmail.com \
    --cc=vdye@github.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).