| Re: [linuxtools-dev] Proposing a single git repository for the project |
When you view 'git log', you only see the log messages for the chain of commits leading back from the commit you currently have checked out. If there are two root commits (and thus two entirely independent trees) in the repository, then the branches of one tree would never share any commits in common with the branches of the other tree, so your requirement of not seeing "unrelated commits" would be met. In fact, you could configure git so that 'git fetch' only pulls objects that are reachable from the eclipse-build branch(es), so you wouldn't even be wasting time downloading data for the other tree. Keep in mind, though, that even if eclipse-build were a subdirectory in the same tree as the rest of Linux Tools, you could still view the log only for that directory by saying 'git log eclipse-build'. It's faster to execute than it is to type. ;-) On Saturday, 22 January 2011, at 5:43 am, Niels Thykier wrote: > On 2011-01-22 02:33, Matt Whitlock wrote: > > 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. > > > > > > [...] > > Personally I work on very few subprojects inside LinuxTools (currently > only eclipse-build); my main concern is whether I will be able to > quickly get up to date with changes in these subprojects without having > to filter unrelated commits out of the log (from other subprojects). > So if these separate root commits would allow me to do that, then I > think I will not have any issues with having everything in a single > repository. > > ~Niels
Attachment:
smime.p7s
Description: S/MIME cryptographic signature