News for hackers. Stuff that matters.
Re:Git 2.5.0 by jacquesm on Tuesday July 28, 2015 @01:21PM (#9963094)
This interests me quite a bit because I've been - forever - busy migrating a huge svn repo to git and the one thing that I keep running into is that 'subrepositories' doesn't quite cut it. Historically my svn is my datastore and I never bothered to set up multiple repositories.

Github might very well be financially impacted if repositories that are now separate for technical reasons will be merged to become subtrees of one larger repository.

Re:Git 2.5.0 by saidajigumi on Tuesday July 28, 2015 @01:55PM (#9963312)
IIUC, your use case is commonly known as subdirectory checkouts. These can be done with git's sparse checkout facility[1], but you still have to make a full repository clone to create a sparse checkout.

To clarify, multiple worktree support creates multiple checkout trees for one (local) .git repo directory. I.e. instead of the old two-clone way of having two working trees:

    $ git clone <URL>/foo.git foo1

    $ git clone <URL>/foo.git foo2
Now it's possible to do this:

    $ git clone <URL>/foo.git foo1

    $ cd foo1

    $ git worktree add ../foo2
    Enter ../foo2 (identifier foo2)
    Switched to a new branch 'foo2'
N.B.: with multiple worktree support, a given branch name can only be checked out to one worktree at a time. E.g. following from the above example:

    $ cd ../foo2

    $ git co master
    fatal: 'master' is already checked out at '/path/to/foo1/.git'
Of course, in this workflow the new "foo2" branch will also be pointing at HEAD of origin/master. It's just that the local repo can only have one worktree pointing at a local branch at a time, otherwise git would have to automatically juggle some ugly and off-topic file synchronization stuff.

[1] http://jasonkarns.com/blog/subdirectory-checkouts-with-git-s...

edit: fixed a couple of confusing typos.

Re:Git 2.5.0 by smcgivern on Wednesday July 29, 2015 @04:51AM (#9967184)
The worktrees in this case are git branches, though. While this is convenient in some cases, it doesn't seem practical to me to have all of a group's code in one repo, but in different branches - it feels like it's fighting the git data model. (And to your closing point, it certainly feels like it's fighting the GitHub UI.)

This might be me misunderstanding how your large svn repo was arranged, though. Could you describe that further?