PEP 385: introduce section on newline issues.
This commit is contained in:
parent
ad94c1d76e
commit
399631d0a3
15
pep-0385.txt
15
pep-0385.txt
|
@ -200,6 +200,21 @@ developed and deployed. The following hooks are being used:
|
||||||
registered contributors. Then, the hook might warn users that push a group
|
registered contributors. Then, the hook might warn users that push a group
|
||||||
of revisions containing changesets from unknown contributors.
|
of revisions containing changesets from unknown contributors.
|
||||||
|
|
||||||
|
End-of-line conversions
|
||||||
|
-----------------------
|
||||||
|
|
||||||
|
There has been some discussion about the lack of end-of-line conversion support
|
||||||
|
in Mercurial. While Mercurial comes with a win32text extension that provides
|
||||||
|
some basic support for converting end-of-line data on a file-name pattern
|
||||||
|
basis, the lack of exclusion (for specifying broad rules with exceptions) and
|
||||||
|
the use of hgrc files (which can't be versioned) make it less than ideal.
|
||||||
|
|
||||||
|
I think the primary line of defense for prevention of inappropriate newlines
|
||||||
|
should be hooks on the server side which basically turn down any changegroup
|
||||||
|
or changeset introducing such data. The use of the win32text extension (which
|
||||||
|
can hopefully be improved/extended to support the usage scenarios mentioned
|
||||||
|
above) and/or a commit-time hook could be the first line of defense.
|
||||||
|
|
||||||
hgwebdir
|
hgwebdir
|
||||||
--------
|
--------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue