I use git to help me synchronize my files between my work machine and home
machine (both Linux based). The bare repository is accessed from my work
machine via SSH. On my home machine, it is on an NFS server. As an aside,
the work machine accesses the NFS server via the home machine via SSH, not
directly from the NFS server.

I noticed when I do a "git pull", git will apparently recompress the data
before sending it. This makes sense to me when it is not local, i.e. from
my work machine, in order to decrease the number of bytes transmitted. But
it doesn't make sense at all when the repository is local (on the local HD
or NFS mounted) because the data is now coming into the machine twice.
First to recompress it, then to transfer it into the working directory.

Now, on my internal gig-ethernet network, this is likely not a big deal.
But I am wonder if it would be a good idea to mention this to the
developers. IOW, are there many people who use a bare repository over a
_slow_ NFS link? Or is it so rare that it would not be worth using up their

Thanks for your thoughts on this.

As of next week, passwords will be entered in Morse code.

Maranatha! <><
John McKown

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to