On Tue, 20 May 2014 18:18:08 +0000
"Stewart, Louis (IS)" <louis.stew...@ngc.com> wrote:
> From you response then there is a method to only obtain the Project,
> Directory and Files (which could hold 80 GBs of data) and not the
> rest of the Repository that contained the full overall Projects?
Please google the phrase "Git shallow cloning".
I would also recommend to read up on git-annex .
You might also consider using Subversion as it seems you do not need
most benefits Git has over it and want certain benefits Subversion has
* You don't need a distributed VCS (as you don't want each developer to
have a full clone).
* You only need a single slice of the repository history at any given
revision on a developer's machine, and this is *almost* what
Subversion does: it will keep the so-called "base" (or "pristine")
versions of files comprising the revision you will check out, plus
the checked out files theirselves. So, twice the space of the files
comprising a revision.
* Subversion allows you to check out only a single folder out of the
* IIRC, subversion supports locks, when a developer might tell the
server they're editing a file, and this will prevent other devs from
locking the same file. This might be used to serialize editions of
huge and/or unmergeable files. Git can't do that (without
non-standard tools deployed on the side or a centralized "meeting
My point is that while Git is fantastic for managing source code
projects and project of similar types with regard to their contents,
it seems your requirements are mainly not suitable for the use case
Git is best tailored for. Your apparent lack of familiarity with Git
might as well bite you later should you pick it right now. At least
please consider reading a book or some other introduction-level
material on Git to get the feeling of typical workflows used with it.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html