Date: Fri, 31 May 2019 16:36:56 +0200 From: Adriaan de Groot <adridg@freebsd.org> To: freebsd-git@freebsd.org Subject: Re: Git handling of commit times Message-ID: <3484239.DPmmpGpFb9@beastie.bionicmutton.org> In-Reply-To: <CAPyFy2AQ4oKwOLkrZ2AgX1FWS2gmic3AD90CO8oSytM=3ZX4OA@mail.gmail.com> References: <8697933A-B813-4088-90B7-A84589C3CD33@freebsd.org> <c1ec3909-eeb8-c852-9167-436e9a0d0e72@gjunka.com> <CAPyFy2AQ4oKwOLkrZ2AgX1FWS2gmic3AD90CO8oSytM=3ZX4OA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3004839.fqq9MUTMxn Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" On Thursday, 30 May 2019 20:29:47 CEST Ed Maste wrote: > this is all in order to address dteske's concern > about misordering when rendering changes. A lot depends on the rendering tools used, *and* what the conceptual "right" order is. There has been plenty of discussion that shows that that the idea of commit-date vs. push-date is a difficult one. Looking at my commits on branch master on GitHub, I have "commits on May 31" that are 4 hours ago, as well as 3 days ago: I merged a short-lived (but more than one-day) branch today. That might look weird, but it's only *wrong* if I have a-priori decided what the ordering should be (date-of-work, vs date-it's- available-for-others). There's plenty of other visualisers out there. Ports has gitk (from devel/git with the GUI option enabled), devel/qgit, and devel/gitg at the very least. Both qgit and gitk are branch-aware, so they don't linearize the way GitHub does, and it's more immediately obvious that merge-and-push was today, while the work was done on tuesday. Follow-on question would be: are we optimizing tools and procedures for one specific hosting and presentation layer (e.g. GitHub) or is there still room to maneuver there? [ade] --nextPart3004839.fqq9MUTMxn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iHUEABEIAB0WIQTVFBoRsP760fy+Jisy7lRaPghTTwUCXPE8CAAKCRAy7lRaPghT T3dWAP4pyGoSvoq7O5JNx30rRQF+gL1hXmrYBHPrKeaFNILKbAD/aRG3B+Ki5436 dxQJNZdsPNCwce6oZFj0tWyDk2DrQsY= =l4Cw -----END PGP SIGNATURE----- --nextPart3004839.fqq9MUTMxn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3484239.DPmmpGpFb9>