Re: erratic behavior commit --allow-empty
- From
Joachim Schmitz <jojo@schmitz-digital.de>
- Date
- Jan 16, 2013, 12:26 UTC
- Message-ID
- <kd669a$q15$1@ger.gmane.org>
- In-Reply-To
- <alpine.LNX.2.01.1301121927350.15558@nerf07.vanv.qr>
Jan Engelhardt wrote:
Show 10 quoted lines
> On Tuesday 2012-10-02 10:26, Johannes Sixt wrote: >> >> Note that git commit -m A --allow-empty *DID* create a commit. Only, >> that it received the same name (SHA1) as the commit you created >> before it because it had the exact same contents (files, parents, >> author, committer, and timestamps). Obviously, your script was >> executed sufficiently fast that the two commits happend in the same >> second. > > What about introducing nanosecond-granular timestamps into Git?
Not every platform (supported by git) does have a nanosecond clock resolution
Bye, Jojo