On Tue, 12 Jun 2012 10:32:14 +0300
Baruch Burstein <bmburst...@gmail.com> wrote:
> On Tue, Jun 12, 2012 at 1:36 AM, Mike Meyer <m...@mired.org> wrote:
> > On Tue, 12 Jun 2012 00:06:38 +0200
> > Stephan Beal <sgb...@googlemail.com> wrote:
> > > On Mon, Jun 11, 2012 at 10:01 PM, Baruch Burstein <bmburst...@gmail.com
> > >wrote:
> > > > +** (versionable) text files which should have CR+NL line endings
> > > > +** automatically fixed to CR
> > > LOL! As much as i agree with the sentiment, isn't saying "fixed" likely
> > to
> > > alienate users of that other OS?
> > So is there a setting for this variable that breaks text files when
> > you check them out?
> Um..., no. If you "fix" a file, it will also fix your current checkout to
> match the "fixed" file in the repository, but any other open checked-outs
> will get fixed (or get conflicts) when doing an update.
To bad. The only SCM I ever used where we *never* had line ending
problems behaved that way. Only it wasn't optional, and they described
it as "line endings are converted to canonical form when you check in
text files, and converted to the local representation when you check
files out" (this was before Apple had switched to Unix, Macs still
used \r).
> This setting is most likely useful for new repositories or existing ones
> that already make sure to use only UNIX line endings. It will likely mess
> up repositories with existing Windows line endings.
True either way. And unfortunately, not fixable. You might be able to
correct the source code in a single commit to isolate the changes, but
history is immutable.
<mike
--
Mike Meyer <m...@mired.org> http://www.mired.org/
Independent Software developer/SCM consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
