From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: jnareb@gmail.com, git@vger.kernel.org
Subject: Re: [RFC][GSoC] Implement Generation Number v2
Date: Mon, 23 Mar 2020 17:02:31 +0530 [thread overview]
Message-ID: <20200323113231.GA22065@Abhishek-Arch> (raw)
In-Reply-To: <xmqq369z7i1b.fsf@gitster.c.googlers.com>
On Sun, Mar 22, 2020 at 10:32:32PM -0700, Junio C Hamano wrote:
> Abhishek Kumar <abhishekkumar8222@gmail.com> writes:
>
> >> Unfortunately for the time being we cannot use commit-graph format
> >> version; the idea that was proposed on the mailing list (when we found
> >> about the bug in handling commit-graph versioning, during incremental
> >> commit-graph implementation), was to create and use metadata chunk or
> >> versioning chunk (the final version of incremental format do not use
> >> this mechanism). This could be used by gen2 compatibile Git to
> >> distinguish between situation where old commit-graph file to be updated
> >> uses generation number v1, and when it uses v2.
> >>
> >> If you have a better idea, please say so.
> >
> > We could also use a flag file. Here's how it works:
> >
> > If the file `.git/info/generation-number-v2` exists, use gen2.
> > Otherwise use gen1.
>
> If the file is lost then we will try to read the other file that has
> the commit-graph data as if it were in old format? And if such a
> file was created (say, with "touch .git/info/generation-number-v2"),
> a file in the original format will be read as if it is in new
> format? If that is the case, it is likely that we'd see a segfault;
> sounds too brittle to me.
Agreed. Flag file has too many issues to be pursued further.
>
> It appears that the format of "CDAT", and the fact that generation
> is represented as higher 30-bit of a be32 integer, is very much
> hardcoded in the design and is hard to change, but your new version
> of graph file can be designed not to use "CDAT" chunk at all, and
> instead have the commit data with new version of generation numbers
> stored in a different chunk (say "CDA2") to force older version of
> Git not to use the new graph file---would that work?
A commit-graph without "CDAT" chunk will hard fail on older versions of
Git. verify_commit_graph_lite() errors out if chunk_commit_data is null.
Metadata chunk seems the way to go.
Regards
Abhishek
next prev parent reply other threads:[~2020-03-23 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 9:35 [RFC][GSoC] Implement Generation Number v2 Abhishek Kumar
2020-03-22 20:05 ` Jakub Narebski
2020-03-23 4:25 ` Abhishek Kumar
2020-03-23 5:32 ` Junio C Hamano
2020-03-23 11:32 ` Abhishek Kumar [this message]
2020-03-23 13:43 ` Jakub Narebski
2020-03-23 15:54 ` Derrick Stolee
2020-03-24 9:24 ` Jakub Narebski
2020-03-23 16:04 ` Junio C Hamano
2020-03-24 15:44 ` Jakub Narebski
2020-03-24 21:13 ` Junio C Hamano
2020-03-26 10:15 ` [GSoC][Proposal v2] " Abhishek Kumar
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=20200323113231.GA22065@Abhishek-Arch \
--to=abhishekkumar8222@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=xmqq369z7i1b.fsf@gitster.c.googlers.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).