git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: Derrick Stolee <stolee@gmail.com>,
	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: Wed, 16 Feb 2022 11:01:24 +0800	[thread overview]
Message-ID: <CAJyCBOSPqP4Rh5ZQhj-DexXXtkwCJTT3tL7DToREfsRR6Hozxg@mail.gmail.com> (raw)
In-Reply-To: <e81f044d-8c3a-90df-ff9e-719b613807d6@gmail.com>

On Tue, Feb 15, 2022 at 2:45 AM Philippe Blain
<levraiphilippeblain@gmail.com> wrote:
> 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!

I read the [1] and this "<rev>^-" syntax seems to exclude the first
parent of <rev>.
In another word, it only gets the part of history within the checked-out
new branch, i.e. "This is typically useful for merge commits where you
can just pass <commit>^- to get all the commits in the branch that was
merged in merge commit <commit> (including <commit> itself)."

It seems that the checked-out branch has a linear clean history,
and that's why it looks like "completely ignore '--graph'". Actually, it does
not ignore "--graph", e.g.

with "--graph":

* 3c0e417827 Merge branch 'ds/fetch-pull-with-sparse-index'
* 408c51f0b4 test-read-cache: remove --table, --expand options
* c2a2940510 t1091/t3705: remove 'test-tool read-cache --table'
* 3a9a6ac5d9 t1092: replace 'read-cache --table' with 'ls-files --sparse'
* 78087097b8 ls-files: add --sparse option
* 5a4e0547e2 fetch/pull: use the sparse index

w/out "--graph":

3c0e417827 Merge branch 'ds/fetch-pull-with-sparse-index'
408c51f0b4 test-read-cache: remove --table, --expand options
c2a2940510 t1091/t3705: remove 'test-tool read-cache --table'
3a9a6ac5d9 t1092: replace 'read-cache --table' with 'ls-files --sparse'
78087097b8 ls-files: add --sparse option
5a4e0547e2 fetch/pull: use the sparse index

Look at the asterisks prefixing every commit in the with "--graph" part.
If you init a new repo and add a few commits to form a linear history,
you will get a similar result by "git log --oneline --graph".

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

-- 
Thanks & Regards,
Shaoxuan

  parent reply	other threads:[~2022-02-16  3:01 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
2022-02-15  2:29     ` Shaoxuan Yuan
2022-02-16  3:01     ` Shaoxuan Yuan [this message]
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=CAJyCBOSPqP4Rh5ZQhj-DexXXtkwCJTT3tL7DToREfsRR6Hozxg@mail.gmail.com \
    --to=shaoxuan.yuan02@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=levraiphilippeblain@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).