This happens sometimes if you have different default permissions on the
files, I've found. It seemed to happen going between a mac and a windows
client, for example. This might not be the same problem you're seeing, but
I figured I would chime in, just in case it is of use.

You can ignore changes like this on the client side with:

 git config core.filemode false

Wes

On Mon, Jul 2, 2012 at 2:15 PM, PJ Weisberg <pjweisb...@gmail.com> wrote:

> On Monday, July 2, 2012, Avner Tamir <avner.ta...@hp.com> wrote:
> > ,Hi
> >
> >
> >
> > I’ve set git server on RHEL 5.6 box, running on httpd
> >
> > we’ve encountered the following scenario several times
> >
> >  User A pushes to remote
> >
> >    User B pull from remote
> >
> >  User B sees the sources pushed by user A as to be committed in his
> local repository
>
> That sounds like a reasonable description of what "pull" does. What did
> you expect/want to see?
>
> --
> -PJ
>
> Gehm's Corollary to Clark's Law: Any technology distinguishable from
> magic is insufficiently advanced.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to