Line ending translation extension

[Martin Geisler]

Matt Mackall <mpm at selenic.com> writes:

> This discussion is way too nebulous. It needs to have one or more
> discrete complete proposals, with all the details in one place.

I was hoping that bringing code to the table would make people sit down,
look at it and contribute. People can at least try out the scenarious
they fear and document them as test cases.

> In Python-land, this is called a PEP. Around here, we do something
> called a Plan. A Plan should:
>
> a) lay out the problem
> b) lay out the alternative and their advantages and shortcomings
> c) elaborate on the preferred solution
> d) describe the steps needed to get from here to there
>
> Usually, these live on the wiki. Here are some existing Plans:
>
> http://mercurial.selenic.com/wiki/?action=fullsearch&context=180&value=plan

Looking at the existing plans, I really think they should

e) indicate the current status. Python PEPs use accepted, rejected,
   withdrawn, deferred, final, active, draft, or replaced.

Otherwise I think they make the project look incomplete. I've seen
people come to IRC asking when we're going to do the rebase command
they've read about on the RebasePlan and RebaseProject pages (and that
was long after the rebase extension was a standard extension).

So I've now added a page here -- with a status! :-)

  http://mercurial.selenic.com/wiki/EOLTranslationPlan

Please create accounts on the wiki and edit away!

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090914/66dacb6d/attachment.pgp