From: Derrick Stolee <email@example.com> To: Jakub Narebski <firstname.lastname@example.org> Cc: "Mike Hommey" <email@example.com>, "SZEDER Gábor" <firstname.lastname@example.org>, email@example.com Subject: Re: [RFC/PATCH] commit-graph: generation v5 (backward compatible date ceiling) Date: Wed, 18 Sep 2019 08:26:41 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 9/18/2019 4:43 AM, Jakub Narebski wrote: > Derrick Stolee <firstname.lastname@example.org> writes: >> On 6/25/2019 3:51 AM, Jakub Narebski wrote: >>> Jakub Narebski <email@example.com> writes: >>>> Derrick Stolee <firstname.lastname@example.org> writes: > [...] >>>> O.K., so the "generation number v2 (legacy)" would be incremental and >>>> backward-compatibile in use (though not in generation and validation). > [...] >>>> Do you have benchmark for this "monotonically offset corrected commit >>>> date" generation number in https://github.com/derrickstolee/git/commits/reach-perf >>>> and https://github.com/derrickstolee/gen-test ? >>> >>> I guess this will have to wait... >> >> I have not had time to revisit this topic and re-run performance >> numbers, sorry. > > I have created pull requests against `reach-perf` branch of > derrickstolee/git repository, and companion pull request against > gen-test repository with proposed prototype of backward-compatible > corrected commit date (with monotonic offsets). > > Could you please run the tests for this generation number v5? I'll try to get to this, but it may take a few days. > I was not > able to do so. It was my first time trying to compile Git on MS > Windows, and while there were no problems compiling `master` (well, > except for compilation taking a long time), I was unable to do it for > `reach-perf` branch because of independent of change compilation errors. I don't think I tested this on Windows. I do most of my performance tests in Linux, especially when presenting numbers to the mailing list. The gen-test repo has a bunch of shell scripts that I used for testing in that environment. Thanks, -Stolee
next prev parent reply other threads:[~2019-09-18 12:26 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-18 0:54 Revision walking, commit dates, slop Mike Hommey 2019-05-18 1:50 ` SZEDER Gábor 2019-05-18 3:58 ` Mike Hommey 2019-05-18 4:17 ` Mike Hommey 2019-05-18 12:01 ` SZEDER Gábor 2019-05-19 22:28 ` Jakub Narebski 2019-05-20 1:33 ` Derrick Stolee 2019-05-20 11:02 ` Jakub Narebski 2019-05-20 11:20 ` Derrick Stolee 2019-05-20 13:42 ` Jakub Narebski 2019-05-20 23:27 ` Jakub Narebski 2019-05-21 1:20 ` Derrick Stolee 2019-05-22 18:29 ` Jakub Narebski 2019-05-22 19:06 ` Derrick Stolee 2019-05-23 21:04 ` Jakub Narebski 2019-06-25 7:51 ` Jakub Narebski 2019-06-25 10:54 ` Derrick Stolee 2019-09-18 8:43 ` [RFC/PATCH] commit-graph: generation v5 (backward compatible date ceiling) Jakub Narebski 2019-09-18 12:26 ` Derrick Stolee [this message] 2019-05-21 13:14 ` [PATCH] revision: use generation for A..B --topo-order queries Derrick Stolee 2019-05-21 13:59 ` [PATCH 2/2] revision: keep topo-walk free of unintersting commits Derrick Stolee 2019-05-22 2:19 ` Mike Hommey 2019-05-21 2:00 ` Revision walking, commit dates, slop Jonathan Nieder
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC/PATCH] commit-graph: generation v5 (backward compatible date ceiling)' \ /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
Code repositories for project(s) associated with this 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).