From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Allow the ident attribute to include a length specifier
Date: Mon, 14 May 2007 14:29:54 +0100 [thread overview]
Message-ID: <200705141429.58412.andyparkins@gmail.com> (raw)
In-Reply-To: <200705141405.29550.andyparkins@gmail.com>
On Monday 2007 May 14, Andy Parkins wrote:
> When the ident attribute is found for a path, then git replaces $ident$
> with:
>
> $ident: df2a1fd3ebce86876721bd7e12ce02ac89c885db $
Is it too late to request a change to this? Make the field $Id$. $Id$ is
present already in SVN and CVS; it would mean that people converting their
existing repositories won't have to make any changes to the source files
should they want to make use of the ident attribute.
Given that it's a feature that's meant to calm those very people, it seems
obtuse to make them edit every file just to make use of it.
I think that bzr uses $Id$; Mercurial has examples for $Id$; monotone has $Id$
on its wishlist. I can't think of a good reason not to stick with the
de-facto standard and call ours $Id$ instead of $ident$.
(I accept that this doesn't help those using $Author$, $Rev$, etc, but it's
better than nothing)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-05-14 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:05 [PATCH] Allow the ident attribute to include a length specifier Andy Parkins
2007-05-14 13:29 ` Andy Parkins [this message]
2007-05-14 13:37 ` [PATCH] Use $Id$ as the ident attribute keyword rather than $ident$ to be consistent with other VCSs Andy Parkins
2007-05-14 14:19 ` Johannes Sixt
2007-05-14 14:39 ` Andy Parkins
2007-05-14 14:54 ` Junio C Hamano
2007-05-14 22:24 ` Andy Parkins
2007-05-15 0:17 ` Junio C Hamano
2007-05-15 2:03 ` Junio C Hamano
2007-05-15 8:14 ` Andy Parkins
2007-05-15 8:54 ` Junio C Hamano
2007-05-15 10:34 ` Andy Parkins
2007-05-17 13:53 ` [PATCH] Allow the ident attribute to include a length specifier Andy Parkins
2007-05-17 19:55 ` Junio C Hamano
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=200705141429.58412.andyparkins@gmail.com \
--to=andyparkins@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.
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 NNTP newsgroup(s).