threads / discuss / 23834

git pull

Subject: git pull

## tl;dr

3 messages between May 17, 2010 and May 19, 2010.

replies: 2people: 3as markdown or json

matteo brutti· May 17, 2010, 21:51 UTC · lore

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· May 18, 2010, 16:31 UTC · re: matteo brutti · lore

Re: git pull

The 17/05/10, matteo brutti wrote:

> Hi,

Hi,

Show 5 quoted lines

> 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/<something>" 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· May 19, 2010, 11:03 UTC · re: matteo brutti · lore

Re: git pull

On 17 May 2010 15:51, matteo brutti <webmbackslash@gmail.com> wrote:

Show 15 quoted lines

> 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.