[Cuis] (no subject)
Angel Java Lopez
ajlopez2000 at gmail.com
Wed Feb 20 05:54:57 CST 2013
Ummm.. Hannes, can you describe:
- The current state
- The desired state
I don't know if the problem is:
- Public repo is ok, all is LF
- But in my dev machine I still see CR/LF, I don't want them
or
- Public repo is ok, all is LF
- But in my dev machine I want CR/LF
or
- Public repo has files with CR/LF
- My dev machine is guilty: some of its files are with CR/LF, and it
pushed them to global repo. The desired state is that repo had only LF
files
I forget the initial use case :-)
Is a problem that hurts dev machine?
Or is a problem that hurts shared repo?
On Wed, Feb 20, 2013 at 8:46 AM, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> Hello Ken
>
> I am sorry that this CR/LF still is an issue.
>
> The last change I pushed to
>
> https://github.com/KenDickey/Cuis-Unicode
>
> was
>
> https://github.com/KenDickey/Cuis-Unicode/blob/master/UniCodesTests.pck.st
>
> It is considered to be a binary file by github, so the commit button
> does not show the difference.
>
> I am using Windows 7 and have on the bash command line
>
> $ git config core.autocrlf
> false
>
> Maybe Angel can help here?
>
> Regards
> Hannes
>
>
> Reference:
>
> http://jvuletich.org/pipermail/cuis_jvuletich.org/2013-February/000774.html
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
More information about the Cuis
mailing list