Hi

As is always the way after you post a question to a group, we think
we've figured it out. :)

I suspect Github is using core.autocrlf=false, as it was suspicious
that the lines marked as changed were line that I had edited in the
previous commits. So my push to github probably had it's line endings
converted by github, which then resulted in a difference when those
same changes were pulled to a different machine.

We have just run a test by setting our autocrlf=false, and pushing and
pulling from a completely new test repo on github. The result were as
expected: no changes except where lines had actually been modified. So
we are now going to reimport the entire repo for our product back into
a brand new github repo with autocrlf=false. I understand that this is
non-optimal, but I don't see an alternative unless we can change the
settings on our github repo. I will post a message on their group to
see what they say.

L

On Apr 7, 3:33 pm, [EMAIL PROTECTED] wrote:
> Hello:
>
> On Apr 7, 9:07 pm, Lee Henson <[EMAIL PROTECTED]> wrote:
>
> > I'm seeing some odd behaviour (well, odd to me anyway) on vista here.
> > Scenario:
> > - 2 machines running the preview20080301 installer
> > - repository on github.com
>
> Could you try making the shared repository local instead of github,
> just to test?
> I believe github is still invite-only?
>
> > Investigation using git-gui shows each file has 1-n lines different,
> > but in each case the "changed" lines still appear to be identical to
> > their "unchanged" state. This feels like crlf again, but then why
> > would a single line be different while the rest of the file is
> > unchanged? Some files have every single line marked different.
>
> What does git-diff say?
> What kind of file is the single line change file?
>
> Best regards,
> Clifford Caoile

Reply via email to