From: Barry Fishman <barry_fishman@acm.org>
To: git@vger.kernel.org
Subject: Re: RCS keyword expansion
Date: Fri, 12 Oct 2007 13:05:01 -0400 [thread overview]
Message-ID: <m3y7e8jmbm.fsf@barry_fishman.acm.org> (raw)
In-Reply-To: Pine.LNX.4.62.0710120726470.11771@perkele.intern.softwolves.pp.se
Peter Karlsson <peter@softwolves.pp.se> writes:
> Yes, but not embedded in the page in a format that is visible to the
> visitor. For CVS I use something like this:
>
> <p class="date">$Date$</p>
>
> to embed the last update time into the page.
>
I guess everyone moving from CVS/SVN to Git faces rethinking of
what the RCS markers really mean in the context of their project.
In my case the identifier was just a away of seeing when the file was
last changed, and who did it. I decided this fit better as an editor
function, rather than a checkin function.
I changed my editor (Emacs) to convert RCS Ids to timestamps when I
opened a file for reading. This would fix old files. When i wrote out
files I would update the timestamp before writing them (via emacs's
timestamp package). I didn't have to think about it as my RCS Id
stamped files slowly evolve into my editor stamped ones. I'm sure I
could do something similar in VIM, or with a script encapsulating
another editor.
This actually worked out better for me. Now the timestamps were updated
even when I hadn't yet checked in the file. Since I test things before
checking them in, I did not have my file changed after testing by the
checkin process.
I could find the the commit assocated with the file fairly quickly using
"git log" and finding the commit for the file just after its timestamp.
--
Barry Fishman
next prev parent reply other threads:[~2007-10-12 17:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 14:47 RCS keyword expansion Peter Karlsson
2007-10-11 15:02 ` Johannes Sixt
2007-10-11 15:09 ` Randal L. Schwartz
2007-10-11 15:59 ` Oliver Kullmann
2007-10-11 18:09 ` Alex Riesen
2007-10-11 20:47 ` Johannes Schindelin
2007-10-11 21:35 ` Sam Vilain
2007-10-12 5:26 ` Peter Karlsson
2007-10-12 10:02 ` Johannes Schindelin
2007-10-12 10:50 ` Peter Karlsson
2007-10-12 11:05 ` Johannes Sixt
2007-10-12 11:21 ` Lars Hjemli
2007-10-12 11:34 ` Johannes Schindelin
2007-10-15 14:03 ` Peter Karlsson
2007-10-15 14:28 ` Johannes Schindelin
2007-10-12 12:57 ` Jan Hudec
2007-10-12 19:08 ` Salikh Zakirov
2007-10-12 22:42 ` Johannes Schindelin
2007-10-12 23:52 ` Zakirov Salikh
2007-10-11 17:55 ` Peter Karlsson
2007-10-11 19:21 ` Alex Riesen
2007-10-12 5:27 ` Peter Karlsson
2007-10-12 17:05 ` Barry Fishman [this message]
2007-10-12 17:44 ` Linus Torvalds
2007-10-12 17:51 ` Florian Weimer
2007-10-11 21:20 ` Sam Vilain
2007-10-11 19:16 ` Lars Hjemli
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=m3y7e8jmbm.fsf@barry_fishman.acm.org \
--to=barry_fishman@acm.org \
--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).