RE: line-ending conversion and keyword substitution

From: Ben Collins-Sussman [mailto:sussman@collab.net]

>Billy, please keep the dev list cc'd. :-)

Argh! Sorry again. I hate how mailing lists all behave differently.

>Billy Tanksley <btanksley@hifn.com> writes:

>> I don't really like the idea of expanding keywords after a
>> commit; I vote
>> for only expanding them after a checkout. If you commit a
>> new file and want to see its keywords, check it out.

>But think about this. I have a document with a $LastChangedDate$
>keyword in it, although it's expanded to some older date. I edit the
>file, then commit. Shouldn't that expanded keyword now reflect
>today's date? I just committed it, after all.

No. Why should it reflect today's date at this point? Who would expect
that? If you want it to, isn't it easy to run an update? Why should
keywords break a nice, consistent, and useful rule? For that matter, why
should it be impossible to commit from a read-only repository (maybe you
brought a CDROM to work after working on the project at home)?

BTW, someone else pointed out that if keywords are expanded after checkin,
the resulting file is different from the checked-in file; I don't think
that's a relevant objection, since the diff procedure should collapse
keywords and normalize line endings if those transforms are enabled.

-Billy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006