| Re: [linuxtools-dev] Proposing a single git repository for the project |
I am not a developer for Linux Tools, but I'll interject in this discussion briefly to mention that you don't necessarily need a separate repository for eclipse-build. You can have more than one root commit in a git object database. I don't know if that would really offer any advantages over having two separate repositories, though it might make it slightly nicer if you ever have reason to move/copy code between eclipse-build and the rest of the projects. On Friday, 21 January 2011, at 8:06 pm, Benjamin Drung wrote: > Am Freitag, den 21.01.2011, 16:29 -0500 schrieb Andrew Overholt: > > Hi, > > > > We need to decide on our git repository structure. I propose we retain > > one repository. The structure can remain the same as it is now in SVN: > > > > org.eclipse.linuxtools.git/ > > autotools/ > > changelog/ > > eclipse-build/ > > gcov/ > > gprof/ > > libhover/ > > lttng/ > > man/ > > oprofile/ > > p2-update-checker/ > > proctools/ > > profiling/ > > releng/ > > rpm/ > > rpmstubby/ > > sdktests/ > > systemtap/ > > valgrind/ > > > > Is anyone against this? > > I would prefer to have a separate repository for eclipse-build. > >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature