On 3/5/2011 7:37 PM, "Martin v. Löwis" wrote:
I am trying to fix the hgeol settings for the vcproj files, with little
success so far. I created
http://hg.python.org/sandbox/hgeol/
which merely changes the .hgeol file. Now, if you enable the eol
extension, and check this branch out, you immediat
Martin v. Löwis:
> So how can I fix this properly: so that all files have CRLF, but
> are still attributed to whoever last modified them, rather than
> having them attributed to me?
I don't think this is possible from the current state. It may be
possible to change the conversion process to 'r
"Martin v. Löwis" writes:
> This is what I refer to as YAGNI. Subversion has LF as the internal
> storage, and, IIRC, so does CVS. I don't think there is any precedence
> for wanting something else - and frankly, I can't see how repository
> storage would matter.
Well, internally you could us
"Martin v. Löwis" writes:
>> Can anyone (re-) post the specification of the proposed extension, to
>> the level that it is currently defined?
>
> For reference, here are the original specification, mine and Martin
> Geisler's:
>
> http://mail.python.org/pipermail/python-dev/2009-August/090984.htm
> Right, but I am just thinking about how we specify in .hgeols what the
> repository is expected to be as this extension might work out nicely
> for other projects who prefer CLRF as their repo-native line ending.
This is what I refer to as YAGNI. Subversion has LF as the internal
storage, and, I
On Sat, Sep 5, 2009 at 15:06, "Martin v. Löwis" wrote:
>>> - Martin Geisler also proposes that there is a section
>>> [repository]
>>> native =
>>> I personally feel YAGNI; it should only support LF (adding such
>>> a feature later may be considered)
>>
>> Do you mean what native is in the repo or
>> - Martin Geisler also proposes that there is a section
>> [repository]
>> native =
>> I personally feel YAGNI; it should only support LF (adding such
>> a feature later may be considered)
>
> Do you mean what native is in the repo or what it should be considered
> on the user's machine?
The
On Sat, Sep 5, 2009 at 07:18, "Martin v. Löwis" wrote:
>> Can anyone (re-) post the specification of the proposed extension, to
>> the level that it is currently defined?
>
> For reference, here are the original specification, mine and Martin
> Geisler's:
>
> http://mail.python.org/pipermail/python
