[git-users] What is best practice to manage a set of repos?

I've just moved a monolithic svn repo to git, and divided it into multiple git repos, one per project. Generally, this is the structure I want. There is one project per repo and, while I do work on multiple projects in any given week, each check-in will be local to a single project. But, I

[git-users] Rebasing large commit-set including merges

Hi, I try to rebase our whole history (~1500 commits) onto a quite empty branch, only including a single commit (creating the base-directory - so there is nothing conflicting in there). I want to do this, because our project was developed on a git-repository but now we have to make our stuff

[git-users] Re: What is best practice to manage a set of repos?

We've been using gitslave http://gitslave.sourceforge.net/ for this purpose with some great experiences. Note that it's somewhat untested on Windows though. --

Re: [git-users] Error:non-monotonic index after failed recursive sed command

Re-post from git@vger, in case someone stumbles upon this post: Happy ending! Turns out i have actually made a backup 3 days ago. My other work was on a branch + in a stash. Commits done on a branch were already present in a backup. I was able to get the stash working by copying corrupted .pack

[git-users] rev-parse --is-inside-work-tree never returns false?

I was playing around with some of the information that rev-parse can return and just tried --is-inside-work-tree to see what it would return. As expected, in my working-dir $PROJ, it returns true. Same for within $PROJ/.git and $PROJ/dir_with_nothing_tracked However, when I try git rev-parse

[git-users] Re: rev-parse --is-inside-work-tree never returns false?

On Tuesday, January 15, 2013 3:24:34 AM UTC+1, Tim Chase wrote: I was playing around with some of the information that rev-parse can return and just tried --is-inside-work-tree to see what it would return. As expected, in my working-dir $PROJ, it returns true. Same for within $PROJ/.git