I think this is the ideal solution. Both sides are satisfied.
+1 (or whatever ;)). Nothing to add.
cmpilato@collab.net(cmpilato@collab.net)@2001.12.13 10:48:02 +0000:
> I posted this earlier with the subject "50% Serious Newline conversion
> suggestion". Well, after reading all the other proposals, and finding
> them all lacking in at least one area, I feel compelled to repost this
> as a 100% serious suggestion, and I actually DO want feedback on it
> now. :-)
>
> In this system:
>
> - newline styles in the repository change ONLY when it was
> intentional.
>
> - we do the world a favor by promoting the use of tools that can
> understand (and not munge) files of various newline styles, while
> not punishing those who fail to use such tools.
>
> - no conversion takes place autometically, thus preserving my
> idealistic viewpoint that a VC system shouldn't be in the business
> of doing anything but versioning data.
>
> ----
>
> > What if we just did something a bit simpler:
> >
> > 1. Do not provide automatic newline conversion.
> >
> > 2. At commit time, compare the newlines used on the edited files with
> > those in text-base, and if the style differs, error "Newline style
> > has changed. To override, use --force, else please restore the
> > file to its original newline convention."
> >
> > 3. Optional: provide an 'svn newline' subcommand which will perform
> > the restoration.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
--
dharana <dharana@dharana.net> Black holes are where
PGP KeyID: 0xC32A724 GOD is dividing by zero
- application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:52 2006