Re: [Gnu-arch-users] missing feature: text file handling

[John Meinel]

Aaron Bentley wrote:
> address@hidden wrote:
>
> > Is it worth it? I don't know[1]. I'd imagine that it might be
> > easier to use an editor `in the know' which respects the particular
> > `line termination conventions'' of a file. Then it'd be rather
> > a project policy thing whether the people involved care. Like
> > tabs/whitespaces in C source, I'd say ;-)
>
>
> Maybe what's desirable is a precommit hook.  When new files or changes 
> don't match the coding policy,
> a) scream and die or
> b) fix them
>
> Aaron

Actually, I would be interested in this. I run into permissions and file 
ending problems all the time. (Editing a file with gvim seems to change 
the permissions, editing it with MSVC changes the line endings, etc.)

The problem is I can't say *all* files must be LF, because MSVC requires 
CR/LF for it's project files. But I suppose you could include exceptions 
in the checkin.

I have the same problem with permissions, because some files I *want* to 
be executable, but most of them I do not.

Maybe something per project/directory, like .arch-inventory/=tagnames. 
Something that would set permission bits, and line endings, with a 
possible global one in ~/.arch-params.

I've never written a hook script before, so I'm not very familiar with 
it. But maybe it's time for me to get over it.

John
=:->

signature.asc
Description: OpenPGP digital signature