Re: Finer timestamps and serialization in git
- From
Eric S. Raymond <esr@thyrsus.com>
- Date
- May 16, 2019, 00:35 UTC
- Message-ID
- <20190516003522.GD124956@thyrsus.com>
- In-Reply-To
- <871s0zwjv0.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com>:
> You put it key-values in the commit message and read it back out via > git-interpret-trailers.
Speaking as a person who has done a lot of repository migrations, this makes me shudder. It's fragile, kludgy, and does not maintain proper separation of concerns.
The feature I *didn't* ask for at the next format break is a user-modifiable key-value store per commit that is *not* in the commit comment. Bzr has this. It's useful.
-- <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>