From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>, Johannes Sixt <J.Sixt@eudaptics.com>
Subject: Re: [PATCH] Use $Id$ as the ident attribute keyword rather than $ident$ to be consistent with other VCSs
Date: Mon, 14 May 2007 23:24:01 +0100 [thread overview]
Message-ID: <200705142324.02929.andyparkins@gmail.com> (raw)
In-Reply-To: <7v646vo3pn.fsf@assigned-by-dhcp.cox.net>
On Monday 2007, May 14, Junio C Hamano wrote:
> My take when I did the $ident$ stuff on this issue was quite the
> opposite. CVS "$Id$" means quite a different thing (pathname,
You're right, but I think it's intended as a unique identifier rather
than that specific information. If that were wanted by a CVS/SVN user
they would have used $Author$, $Rev$, $Date$, etc. $Id$ to me was just
some way of identifying the file its in uniquely - the fact that git
has a much better way of doing that is a bonus, and is exactly right
for $Id$ IMHO.
> per-file revision number, date, and status) and it would not be
> right to overwrite it with $ident$ which does not record any of
> those "context sensitive" information.
It would be perfectly correct to overwrite it, as in the repository
version none of that information is present, and even if it wasn't, as
we've discussed at length, it's all meaningless in a git context
anyway - the best thing that you could do for it _is_ overwrite it.
> I did not think other systems making that mistake was not an
> excuse for us to do so, but on the other hand, if the users of
> those other systems are happy to lose the information from CVS
> then perhaps the users do want $Id$.
As I said, there is no information in that field when we import from
CVS/SVN - the repository versions are stored with the fields
collapsed - so you are not overwriting anything, and therefore not
losing information.
> Obviously I do not care much about this feature and I have not
> look at Andy's patch too deeply yet, but in any case I think the
> inverse conversion needs to be modified to match it, if it
> hasn't been done so.
I believe I did the inverse conversion as well. It's only rough, in the
end I don't care much either way - I've already converted everything of
mine to git so it affects me not at all. I offer it only as a
suggestion for imports from other repositories.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-05-14 22:24 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
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 [this message]
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=200705142324.02929.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).