Re: Git commit generation numbers
- From
Shawn Pearce <spearce@spearce.org>
- Date
- Jul 21, 2011, 20:33 UTC
- Message-ID
- <CAJo=hJsi-cVdNC+T4RiwXdsjypL3FPc8gPOL5qL9=tGj05xPGg@mail.gmail.com>
- In-Reply-To
- <20110721202722.3765.qmail@science.horizon.com>
On Thu, Jul 21, 2011 at 13:27, George Spelvin <linux@horizon.com> wrote:
Show 5 quoted lines
> > be enough for the time being. As a local cache, it can be extended > with a software upgrade. There's no need to ever have support for two > formats in any given release; just notice that the cache format is wrong, > blow it away, and regenerate it.
Don't assume that. Consider a repository stored on NFS that is read-only to you. The NFS server has one version of Git installed, and is using cache format A. You have a newer version of Git installed on your workstation, using cache format B. Now you cannot use this repository as a local filesystem... its only available to you over the Git protocols. This breaks a number of people's environments. :-)
Its better if we can avoid having to change file formats very often, even if they are a local "cache".
-- Shawn.