From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Finer timestamps and serialization in git
Date: Wed, 15 May 2019 20:35:22 -0400 [thread overview]
Message-ID: <20190516003522.GD124956@thyrsus.com> (raw)
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>
next prev parent reply other threads:[~2019-05-16 1:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 19:16 Finer timestamps and serialization in git Eric S. Raymond
2019-05-15 20:16 ` Derrick Stolee
2019-05-15 20:28 ` Jason Pyeron
2019-05-15 21:14 ` Derrick Stolee
2019-05-15 22:07 ` Ævar Arnfjörð Bjarmason
2019-05-16 0:28 ` Eric S. Raymond
2019-05-16 1:25 ` Derrick Stolee
2019-05-20 15:05 ` Michal Suchánek
2019-05-20 16:36 ` Eric S. Raymond
2019-05-20 17:22 ` Derrick Stolee
2019-05-20 21:32 ` Eric S. Raymond
2019-05-15 23:40 ` Eric S. Raymond
2019-05-19 0:16 ` Philip Oakley
2019-05-19 4:09 ` Eric S. Raymond
2019-05-19 10:07 ` Philip Oakley
2019-05-15 23:32 ` Eric S. Raymond
2019-05-16 1:14 ` Derrick Stolee
2019-05-16 9:50 ` Ævar Arnfjörð Bjarmason
2019-05-19 23:15 ` Jakub Narebski
2019-05-20 0:45 ` Eric S. Raymond
2019-05-20 9:43 ` Jakub Narebski
2019-05-20 10:08 ` Ævar Arnfjörð Bjarmason
2019-05-20 12:40 ` Jeff King
2019-05-20 14:14 ` Eric S. Raymond
2019-05-20 14:41 ` Michal Suchánek
2019-05-20 22:18 ` Philip Oakley
2019-05-20 21:38 ` Elijah Newren
2019-05-20 23:12 ` Eric S. Raymond
2019-05-21 0:08 ` Jakub Narebski
2019-05-21 1:05 ` Eric S. Raymond
2019-05-15 20:20 ` Ævar Arnfjörð Bjarmason
2019-05-16 0:35 ` Eric S. Raymond [this message]
2019-05-16 4:14 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190516003522.GD124956@thyrsus.com \
--to=esr@thyrsus.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).