This sounds like a file portability issue with git. If the other server
happens to be a *nix system, CRLF line ending are interpreted differently
than on a windows system. Git allows you to normalize line endings. Check
in a .gitattributes file in the root of your repository to tell git to
treat these files as binary files. The binary attribute is a macro that
expands to a set of options telling git not to calculate a diff nor impose
CRLF line endings.

echo '*.exe          binary' >> .gitattributes
echo '*.manifest     binary' >> .gitattributes
echo '*.application  binary' >> .gitattributes

For a reference on gitattributes refer to
http://git-scm.com/docs/gitattributes.

- Alex


On Wed, May 7, 2014 at 11:36 PM, Geo P.C. <[email protected]> wrote:

> Please anyone do update on this.
>
>
>
>
>
>
> *Thanks & RegardsGeo P.C.http://pcgeo.blogspot.in/
> <http://pcgeo.blogspot.in/>*
>
>
> On Wed, May 7, 2014 at 11:16 AM, Geo P.C. <[email protected]> wrote:
>
>> We have some .net files (.exe, .manifest & .application) that generated
>> in windows and while we push these files to git server and then when we do
>> a git pull on another web-server the md5sum for some files mostly the exe
>> and .application gets different in web-server but for other files its same.
>>
>> But when we upload these .net files manually to web-server md5sum is
>> same. SO please let me know is there we need to check for getting the
>> proper md5sum value for git files?
>>
>> We are using GitLab 6.3.1 and both gitlab and web-server are Ubuntu 12.04
>> Servers. Can anyone please help us on it.
>>
>> Thanks
>> Geo
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to