Re: Git commit generation numbers
- From
Tony Luck <tony.luck@intel.com>
- Date
- Jul 15, 2011, 18:46 UTC
- Message-ID
- <CA+8MBbJNZdkpOhA5Kke0VqUA9qCFdzfEP5cWPTMF3eUfDsGRiQ@mail.gmail.com>
- In-Reply-To
- <CA+55aFw_XjWm+4XwsN6CRJnsrcEu5YEChOHSHN51UUBN6PynWw@mail.gmail.com>
On Fri, Jul 15, 2011 at 9:44 AM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
Show 6 quoted lines
> Btw, I do agree that we probably should add a warning for the case
> ("your clock is wrong - your commit date is before the commit date of
> your parents") and maybe require the use of "-f" or something to
> override it. That would certainly be a good thing quite independently
> of anything else. So regardless of generation counts, it's probably
> worth it.What if my clock is wrong in the opposite direction - set to some time out in 2025. It would pass the check you propose and let the commit go in - but would cause problems for everyone if that tree was pulled into upstream.
You'd also want a check in pull(merge) that none of the commits being added were in the future (as defined by the time on your machine).
-Tony