On Wed, 17 Nov 2010, Dave Martin wrote: > FYI, I've set up a tree with my currently posted patches, with > branches currently as follows: > > git://git.linaro.org/people/dmart/linux-2.6-arm.git > > Upstreamable branches: > * master : base branch in sync with linus' tree > * arm/* : topic branches for ARM architecture support stuff > * arm-all : merge branch of arm/* (excluding arm/development/ branches) > > Changes appearing in the above branches has either been posted on > upstream lists or is about to be posted. > > Development branches: > * development/* : development versions of upstreamable branches. > > These are more volatile and may not have been discussed upstream. > > Dirty branches: > * dirty/* : hacking branches which are considered unsuitable for upstream > * dirty-all : merge of all interesting changes including dirty ones > > The dirty* branches are not ready for upstreaming: > Don't pull these branches without good reason. > > Do we have a systematic place to document the contents of git trees? > I put the above text in linux-2.6-arm.git/description, but gitweb only > seems to show the first line.
I don't think we do. Maybe a wiki page with that info could do it? I've also received a few inquiries about what the Linaro kernel tree is and what it is not and therefore that information could belong there too. > I'm a bit of a newbie to this, so any comments welcome regarding how > I've set this up. This looks excellent! Nicolas _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
