All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Steven Michalske <smichalske@gmail.com>,
	Thomas Berg <merlin66b@gmail.com>, Jeff King <peff@peff.net>,
	Shawn Pearce <spearce@spearce.org>, git <git@vger.kernel.org>
Subject: Re: Millisecond precision in timestamps?
Date: Thu, 29 Nov 2012 05:38:47 -0500	[thread overview]
Message-ID: <20121129103847.GA9264@thyrsus.com> (raw)
In-Reply-To: <CAMP44s3ShoR7iR5QLYn_u+u_nNGnS1jumpt+iseWYKx0PX9UEA@mail.gmail.com>

Felipe Contreras <felipe.contreras@gmail.com>:
> On Thu, Nov 29, 2012 at 8:11 AM, Junio C Hamano <gitster@pobox.com> wrote:
> > Steven Michalske <smichalske@gmail.com> writes:
> >
> >> Would having arbitrary key value pairs be useful in the git data
> >> model?
> >
> > My answer to the question is that it is harmful to the data model,
> > but the benefit of going against the data model _may_ outweigh the
> > downside.  It is all relative.
> 
> If git doesn't provide the capability, people will keep using the
> commit message to store that extra information, which I would think is
> even more harmful. An standard 'commit-extra' note or something would
> help deal with that.

Agreed.  

My use case for a capability like this is one of the more common ones.
I want to be able to store a fossil commit-ID inherited from another
VCS outside the commit comment.  The absence of a key/value store forces
me into some annoying kludges.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  reply	other threads:[~2012-11-29 10:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 20:48 Millisecond precision in timestamps? Eric S. Raymond
2012-11-27 21:41 ` Shawn Pearce
2012-11-27 22:06   ` Junio C Hamano
2012-11-27 23:04     ` Eric S. Raymond
2012-11-27 23:49       ` Shawn Pearce
2012-11-28  0:12         ` Eric S. Raymond
2012-11-28  0:22           ` David Lang
2012-11-28  0:26           ` Felipe Contreras
2012-11-28  1:07             ` Shawn Pearce
2012-11-28  1:17               ` Jeff King
2012-11-28  1:29                 ` Jason Pyeron
2012-11-28  1:42                 ` Felipe Contreras
2012-11-28  3:23                 ` Eric S. Raymond
2012-11-28  3:30                   ` Jeff King
2012-11-28  3:44                     ` Felipe Contreras
2012-11-28  3:47                     ` Eric S. Raymond
2012-11-28  4:07                       ` Jeff King
2012-11-28  4:25                         ` Eric S. Raymond
2012-11-28  7:29                 ` Junio C Hamano
2012-11-28  7:58                   ` Eric S. Raymond
2012-11-28  8:04                     ` David Aguilar
2012-11-28 10:14                       ` Andreas Ericsson
2012-12-05 23:37                       ` Robin Rosenberg
2012-12-10 20:56                     ` James Cloos
2012-11-28  8:19                   ` Thomas Berg
2012-11-28  8:44                     ` Felipe Contreras
2012-11-28  9:10                       ` Thomas Berg
     [not found]                         ` <E4C993F4-B7A4-4CB6-A9EA-BFE98BE3A381@gmail.com>
2012-11-29  6:16                           ` Eric S. Raymond
2012-11-29  7:11                           ` Junio C Hamano
2012-11-29  7:22                             ` Felipe Contreras
2012-11-29 10:38                               ` Eric S. Raymond [this message]
2012-11-29 16:42                                 ` Junio C Hamano
2012-11-29 19:02                                   ` Eric S. Raymond
2012-11-28 17:57                     ` Junio C Hamano
2012-11-28 10:10                   ` Andreas Ericsson
2012-11-29 19:14                   ` Phil Hord
2012-11-29 20:01                     ` Jeff King
2012-11-28  1:11             ` Eric S. Raymond
2012-11-28  1:36               ` Felipe Contreras
2012-11-28  2:01       ` Junio C Hamano
2012-11-27 21:44 ` Pyeron, Jason J CTR (US)

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121129103847.GA9264@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=merlin66b@gmail.com \
    --cc=peff@peff.net \
    --cc=smichalske@gmail.com \
    --cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.