search for: r354148

...ve and empty file and commit with git > $ git rm empty > $ git commit -m "remove empty file" > # commit/push with svn to the unified git repo > $ git svn dcommit > Committing to https://github.com/joker-eph/llvm-project/trunk/compiler-rt > ... > D empty > Committed r354148 > > > Here is the commit: > https://github.com/joker-eph/llvm-project/commit/5f7e977c8cf3c33153d91be9b556143b49911ebe > > > — > Mehdi > > > > > > > > > > While admittedly you do get a linear history with using the mono-repository, > that isn’...

...y >>> $ git commit -m "remove empty file" >>> # commit/push with svn to the unified git repo >>> $ git svn dcommit >>> Committing to https://github.com/joker-eph/llvm-project/trunk/compiler-rt >>> ... >>> D empty >>> Committed r354148 >>> >>> >>> Here is the commit: >>> https://github.com/joker-eph/llvm-project/commit/5f7e977c8cf3c33153d91be9b556143b49911ebe >>> >>> >>> — >>> Mehdi >>> >>> >>> >>> >>> &gt...

Hi Duncan, > […] > 2. Those working on projects *outside* the monolithic repo will get the downsides of both: a monolithic repo that they are only using parts of, and multiple repos that are somehow version-locked. > > 3. For many (most?) developers, changing to a monolithic git repo is a *bigger* workflow change than switching to separate git repos. Many people (and at least some