Date: Wed, 17 Nov 2021 08:48:40 -0800 From: Mark Millard via freebsd-git <freebsd-git@freebsd.org> To: Stefan Sperling <stsp@stsp.name> Cc: =?utf-8?Q?Ulrich_Sp=C3=B6rlein?= <uqs@freebsd.org>, Graham Perrin <grahamperrin@gmail.com>, freebsd-git <freebsd-git@freebsd.org> Subject: Re: cgit, ages and chronological order Message-ID: <4EB44761-AF88-46DA-9FA5-D40DAC25EAEA@yahoo.com> In-Reply-To: <BCC5C587-7296-47D3-8DDC-311C95637297@yahoo.com> References: <9766b3e1-fb5d-1993-46e2-057e2567315a@gmail.com> <CAJ9axoT6kEwC%2Bt5zHSKPSFgFmaOt8-CXPAG5jsanWobT4LZhpA@mail.gmail.com> <36020FD7-32A4-4869-B6A2-2622F50F6478@yahoo.com> <YZTOE5jPwxXrkgbY@benson.stsp.name> <BCC5C587-7296-47D3-8DDC-311C95637297@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Nov-17, at 08:40, Mark Millard <marklmi@yahoo.com> wrote: > On 2021-Nov-17, at 01:40, Stefan Sperling <stsp@stsp.name> wrote: >=20 >> On Tue, Nov 16, 2021 at 02:32:52PM -0800, Mark Millard via = freebsd-git wrote: >>> author George V. Neville-Neil <gnn@FreeBSD.org> = 2021-11-10 17:51:42 +0000 >>> committer George V. Neville-Neil <gnn@FreeBSD.org> = 2021-11-10 18:09:19 +0000 >>>=20 >>> information being based on local git commit timing (and clocks) >>> vs. when the commits are pushed to FreeBSD servers: The display >>> order is from the timing on the FreeBSD servers but the Age is >>> based on the original commit (before the push). The longer the >>> delay between commit and push, the more noticeable the >>> distinction is. >>=20 >> This is not how Git works. If the server changed the timestamp then >> it would also have to rewrite the commit object and change its hash. >> Git's server will only ever store objects as they arrived on the = wire. >>=20 >> Rather, both timestamps were created locally. >> The above looks as if the author used git-rebase or similar on their = own >> commits. Some Git commands will update the committer field but leave = the >> author field as it is. These fields contain email address and = timestamp. >>=20 >> Generally, sorting commits by committer timestamp will give the order >> most people would expect. Unless some client has an unsynced clock, = and >> nothing can be done about that without a hypothetical smarter server = and >> client which support server-side rewriting of commits during push. >>=20 >=20 > Try doing range searches for each of: >=20 > 8ef0c11e7ce7 > 8ef0c11e7ce7^ > 8ef0c11e7ce7^^ > 8ef0c11e7ce7^^^ > 8ef0c11e7ce7^^^^ >=20 > on the main branch and note where each starts. (These > are in the range that I showed originally.) >=20 > That is the order of the history on the branch on the > FreeBSD server. It does not follow the Age: Age need > not track the sequencing on the branch on the server. Searching for each of the ranges: 8ef0c11e7ce7 8ef0c11e7ce7~1 8ef0c11e7ce7~2 8ef0c11e7ce7~3 8ef0c11e7ce7~4 gets the same results, by the way. Try it that way if you prefer. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB44761-AF88-46DA-9FA5-D40DAC25EAEA>