Possible cover-all solution: use Mercurial's "eol" extension. It's worked
pretty well for me so far, and handily autofixed all the DOS endings in a
particular fork I looked at in one go. It works much like the autoprops
configuration does in Subversion; hopefully with less pain.

Enable it (should be included by default in all recent versions, dunno about
Tortoise) by adding the following section and options to your system-wide or
repo-local .hgrc file:

[extensions]
eol =

Then add a ".hgeol" file to the root of the repository (it can be versioned
and thus easily distributed!), and fill it with whatever standard Mercurial
pattern entries are needed, like so:

[patterns]
**.py = native
**.txt = native
**.h = native
**.cpp = native
**Makefile = LF

As soon as this file exists and the extension is active for you, further hg
commands will immediately treat any non-conforming line-endings as
modifications to your current working copy. Hope this is helpful; if so, it
could be added to that page as well.


Discrete


On Tue, Feb 1, 2011 at 1:54 PM, Celierra Darling <celie...@gmail.com> wrote:

> For those that have already followed the instructions there - the coding
> standard says to prefer tabs, not spaces, which is the opposite of what the
> page was instructing until just now.
>
> Celi
>
>
> On Tue, Feb 1, 2011 at 7:35 AM, Oz Linden (Scott Lawrence) <
> o...@lindenlab.com> wrote:
>
>> Other than a few files that appear to be completely Windows specific,
>> and I did not know for sure did not require them, I've converted all the
>> DOS line endings in viewer-development back to plain linefeeds.  I'll be
>> checking regularly for any that get added (hopefully before they get
>> into the main repo) and advising the perpetrators of the error of their
>> ways...
>>
>> So that I have a resource to direct them to, and to help prevent any new
>> developers from committing this minor sin, we need a set of clear
>> instructions on what Windows tools do this correctly and how to
>> configure them to do so.   Please help by adding to:
>>
>>
>> https://wiki.secondlife.com/wiki/How_to_avoid_DOS_line_endings_in_Windows_tools
>>
>> _______________________________________________
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/OpenSource-Dev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>>
>
>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to