From owner-freebsd-git@freebsd.org Fri May 31 14:37:04 2019 Return-Path: Delivered-To: freebsd-git@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2B3815BEB8C for ; Fri, 31 May 2019 14:37:04 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from lb1-smtp-cloud8.xs4all.net (lb1-smtp-cloud8.xs4all.net [194.109.24.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.xs4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32B5C6EEF6 for ; Fri, 31 May 2019 14:37:04 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from beastie.bionicmutton.org ([62.251.92.29]) by smtp-cloud8.xs4all.net with ESMTP id WieUhCyFe0YQeWieVhIhyx; Fri, 31 May 2019 16:37:03 +0200 From: Adriaan de Groot To: freebsd-git@freebsd.org Subject: Re: Git handling of commit times Date: Fri, 31 May 2019 16:36:56 +0200 Message-ID: <3484239.DPmmpGpFb9@beastie.bionicmutton.org> Organization: FreeBSD In-Reply-To: References: <8697933A-B813-4088-90B7-A84589C3CD33@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3004839.fqq9MUTMxn"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-CMAE-Envelope: MS4wfOaVbmGOgyaQvXRJU5JtCJSR2l2N2HLYE4U3QDgq4+9xNWyFq3XpTRFwV/6FAAMzJv4I2Kw5DMmjjFHkbu//mgAMuDkWvql1xszj1hM4N2yaY1uCVvDe qqMLq78N+odQWR5FAJEW6PVLimyuve64WfGpyJX7gL0IZZYAuG/cdUNafTRrThZn7L+c7QhKpIneFw== X-Rspamd-Queue-Id: 32B5C6EEF6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.975,0]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 14:37:04 -0000 --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--