From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric S. Raymond" Subject: Re: Millisecond precision in timestamps? Date: Thu, 29 Nov 2012 05:38:47 -0500 Organization: Eric Conspiracy Secret Labs Message-ID: <20121129103847.GA9264@thyrsus.com> References: <20121128011750.GA23498@sigill.intra.peff.net> <7v7gp6i3rx.fsf@alter.siamese.dyndns.org> <7va9u0sx26.fsf@alter.siamese.dyndns.org> Reply-To: esr@thyrsus.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Junio C Hamano , Steven Michalske , Thomas Berg , Jeff King , Shawn Pearce , git To: Felipe Contreras X-From: git-owner@vger.kernel.org Thu Nov 29 11:39:21 2012 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Te1WY-0003ll-Mh for gcvg-git-2@plane.gmane.org; Thu, 29 Nov 2012 11:39:19 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753358Ab2K2KjD (ORCPT ); Thu, 29 Nov 2012 05:39:03 -0500 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]:52039 "EHLO snark.thyrsus.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751077Ab2K2KjB (ORCPT ); Thu, 29 Nov 2012 05:39:01 -0500 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 8F4874065F; Thu, 29 Nov 2012 05:38:47 -0500 (EST) Content-Disposition: inline In-Reply-To: X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.21 (2010-09-15) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Felipe Contreras : > On Thu, Nov 29, 2012 at 8:11 AM, Junio C Hamano wrote: > > Steven Michalske 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. -- Eric S. Raymond