Re: Weird shallow-tree conversion state, and branches of shallow trees
- From
- Sven Verdoolaege <skimo@kotnet.org>
- Date
- Apr 16, 2007, 15:54 UTC
- Message-ID
- <20070416155456.GS955MdfPADPa@greensroom.kotnet.org>
- In-Reply-To
- <200704161003.07679.andyparkins@gmail.com>
On Mon, Apr 16, 2007 at 10:03:05AM +0100, Andy Parkins wrote:
> there are two copies of the same file floating around. Which one am I > editing and which one am I printing?
Turn off write permissions on the generated file.
> Have I run the script yet? When I
Use a post-commit hook.
> I'm not just being argumentative - I still have not understood what terrible > evil it is that keyword expansion causes but crlf conversion does not.
For one thing, this keyword expansion thing requires the SCM to modify the file during commit. (Hey, my editor says something changed the file. Do I have the file opened in another session? Oh, it's the stupid keyword expansion!) AFAIU, crlf conversion will not change the working tree copy of your file on commit.
skimo