# git pull 3 messages from 2010-05-17 to 2010-05-19. Participants: matteo brutti, Nicolas Sebrecht, hasen j. Thread: https://gitlist.dev/t/23834 ## matteo brutti, 2010-05-17 21:51 Subject: git pull Message-ID: URL: https://gitlist.dev/e/AANLkTimLZgkojC5L0ZdDewhprLgehLw2w4EZDwyViF4R%40mail.gmail.com ``` Hi, i'm learning about git and soon have a question. My repo is in /dev/sda6 and my home is in /dev/sda4, as are both in local i thought that when i committ, i'll found the files on repo changed, it was not so! I learn i have to use git pull, but i didn't understand why. I made some tries, put my repo in /home/user/myrepo cloned in /home/user/myclones changed files and committed and the changes was in the repo without any need of pulling, and i have permission to write to /dev/sda6, so why have i to pull changes? Thanks. Matteo ``` ## Nicolas Sebrecht, 2010-05-18 16:31 Subject: Re: git pull Message-ID: <20100518163115.GA12950@vidovic> URL: https://gitlist.dev/e/20100518163115.GA12950%40vidovic In-Reply-To: ``` The 17/05/10, matteo brutti wrote: > Hi, Hi, > i'm learning about git and soon have a question. > My repo is in /dev/sda6 and my home is in /dev/sda4, as are both in > local i thought that when i committ, i'll found the files on repo > changed, it was not so! I learn i have to use git pull, but i didn't > understand why. "/dev/sda" is the physical device and "/dev/sda6" a physical partition of the hard drive "sda". Inside a partition, we may find (usually after the installation process of the system) a filesytem. The filesytem contains the files we can access to when mounted to the virtual filesytem (begining at "/"). While using user application which works on usual files (like git does), we don't care about the underlying local hard drive device ("/dev/sda" here). You can safely forget all the "/dev/" things here. > I made some tries, put my repo in /home/user/myrepo cloned in > /home/user/myclones changed files and committed and the changes was in > the repo without any need of pulling, and i have permission to write > to /dev/sda6, so why have i to pull changes? With the above in mind, could you please try to rephrase your problem (and maybe provide a basic use case with the commands to reproduce it) ? -- Nicolas Sebrecht ``` ## hasen j, 2010-05-19 11:03 Subject: Re: git pull Message-ID: URL: https://gitlist.dev/e/AANLkTikDmfiUwhn2wQNVkhTVMUpv2pyp5pU5OvmfzM-T%40mail.gmail.com In-Reply-To: ``` On 17 May 2010 15:51, matteo brutti wrote: > Hi, > i'm learning about git and soon have a question. > My repo is in /dev/sda6 and my home is in /dev/sda4, as are both in > local i thought that when i committ, i'll found the files on repo > changed, it was not so! I learn i have to use git pull, but i didn't > understand why. > I made some tries, put my repo in /home/user/myrepo cloned in > /home/user/myclones changed files and committed and the changes was in > the repo without any need of pulling, and i have permission to write > to /dev/sda6, so why have i to pull changes? > > Thanks. > > > Matteo If you clone repoA into repoB, then you commit some new changes to repoA, you won't see the same changes in repoB unless you pull them from repoA. I don't think it matters whether or not they are in the same partition or not. As far as I understand, if you clone within the same partition, the object database might be hard-linked. This won't affect what files you have checked out though. It would just mean that you won't need to "fetch", because the objects are already there. ```