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>
index | next in thread | raw e-mail
> > Did anyone ever find an elegant solution to preventing the following edge-case? > > 1. Committer uses a VM but keeps it paused most of the time > > 2. Committer unpauses VM and makes a commit without first running ntpdate to correct the clock of the paused VM > > 3. Committer pushes commit with a timestamp that predates the timestamp for the previous commit on the file in-question > > 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 them in wrong order. > > I think there was some talk of a hook to prevent timestamps moving backward with respect to each object being touched in a pushed commit -- is this even possible to prevent? > > Is this no longer an issue? Just looking for clarification on a genuine concern. > -- > Devin Forwarding by request to ML — Devinhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8697933A-B813-4088-90B7-A84589C3CD33>