Date: Tue, 28 May 2019 20:20:05 -0700 From: Devin Teske <dteske@freebsd.org> To: freebsd-git@freebsd.org Cc: dteske@FreeBSD.org Subject: Git handling of commit times Message-ID: <8697933A-B813-4088-90B7-A84589C3CD33@freebsd.org>
next in thread | raw e-mail | index | archive | help
>=20 > Did anyone ever find an elegant solution to preventing the following edge-= case? >=20 > 1. Committer uses a VM but keeps it paused most of the time >=20 > 2. Committer unpauses VM and makes a commit without first running ntpdate t= o correct the clock of the paused VM >=20 > 3. Committer pushes commit with a timestamp that predates the timestamp fo= r the previous commit on the file in-question >=20 > In this case, GitHub renders the commits our of order. If memory serves, "= git log" will show them in the proper order, but github web interface shows t= hem in wrong order. >=20 > I think there was some talk of a hook to prevent timestamps moving backwar= d with respect to each object being touched in a pushed commit -- is this ev= en possible to prevent? >=20 > Is this no longer an issue? Just looking for clarification on a genuine co= ncern. > --=20 > Devin Forwarding by request to ML =E2=80=94=20 Devin=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8697933A-B813-4088-90B7-A84589C3CD33>