[Kde-scm-interest] [PATCH] scripty

[Thiago Macieira]

Chani wrote:
>but my knowledge of git is still fuzzy... would this be no slower than
>checking out the branches? would I still have to have tracking branches
>created, to get a git fetch to actually download the files for the
> remote branches I care about?
>I want to be sure that git's not going to be redownloading all files on
> every reset, or downloading branches I don't actually need, or
> anything.

No, it shouldn't be any slower or faster than checking out a branch.

The process of checking out files is the same: the file tree of the 
corresponding commit is read from the object database, then it is compared 
to the current checkout index. Files that are new are checked out; files 
that are modified are checked out; files that disappear between commits are 
removed.

As for git fetch, it fetches all remote branches into the local copy of 
the remote (refs/remote/origin/*), regardless of which tracking branches 
you may have (refs/heads/*).

So: git reset doesn't download anything, however git fetch does download 
all branches, including those you don't want. 

The solution for that is to have only branches you want in the server. 
Follow Qt's example: only the two main branches are in qt.git. Anybody's 
work is contained in other repositories, like kinetic.git and qt-s60.git.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090602/8276fc7c/attachment-0001.sig