Hi Dennis, On Sun, Jan 04, 2015 at 09:23:52PM -0800, Dennis Ferguson wrote: > On 4 Jan, 2015, at 13:08 , Reinoud Zandijk <reinoud%NetBSD.org@localhost> wrote: > > Sub-brances are used in say the riscv repository to point to specific releases > > of the various tools needed. Nice at first glance but impossible to do a `git > > diff' and get the entire tree. We could avoid these by demananding such things > > to be handled as vendor branches (which they really are) but IMHO its silly > > that git explicitly allows such subrepo's but has only minimal support for > > them. If the marker is changed you can't just `git update' it since then it > > goes to the head of that branch and when you have patches in those trees it > > really gets ugly :-/ > > Is the riscv repository you are talking about this one? > > git://github.com/ucb-bar/riscv-gnu-toolchain See f.e. https://github.com/ucb-bar/riscv-tools > If so I'd like to understand what it is you are calling a "sub-branch", > as I'm not sure what that is. There are various links there to various points in other repositories; those are the types i talked about. These points could be considered vendor branch imports but they are set to specific commit points to ensure that despite further enhancements on each of the brances this checkout contains a working set. With regards, Reinoud
Attachment:
pgpFnrPx8TQ9d.pgp
Description: PGP signature