Mark Struberg> We have one "official" branch for each target board...so > maybe a dozen or so branches.
Chis, to me this sounds more like you abuse SCM branches for what should be into 'modules' In SVN this would make not a big difference (because of the silly svn:copy thingy) but for any sane SCM, tags are not directories!
If you move all your board specific code into child-modules, then you could happily tag over your whole project (including all those modules).
LieGrue, strub
--- Chris Friesen <cfriesen@nortel.com> schrieb am Di, 19.5.2009:
Show 62 quoted lines
> Von: Chris Friesen <cfriesen@nortel.com> > Betreff: Re: any way to apply tag across all branches in repository? > An: "Linus Torvalds" <torvalds@linux-foundation.org> > CC: "Brandon Casey" <casey@nrlssc.navy.mil>, git@vger.kernel.org > Datum: Dienstag, 19. Mai 2009, 23:31 > Linus Torvalds wrote: > > > > On Tue, 19 May 2009, Chris Friesen wrote: > >> The tagging would be done only by the "official" > build process (which > >> pulls from an "official" repository), not by each > designer. Typically > >> the official builds would be done weekly, more > frequently if requested. > > > > Well, you can tag when you do that official build. Do > you really do > > "official" builds from all branches? That sounds a bit > insane. > > We have one "official" branch for each target board...so > maybe a dozen > or so branches. > > Developers do private builds, but they're not tagged. > > > Remember: you don't have to tag whatever is the "top" > - tagging can happen > > later. Tagging at build-time is perfectly fine. > > Tagging at build-time is actually the plan. > > > In fact, I'd suggest going even further. Don't tag the > source branch when > > you build - tag it after it has passed whatever > testing you do (I hope you > > _do_ have some extensive test-suite before release), > and as you actually > > make it public (or whatever you do). Only at _that_ > point, tag the tree > > with "release-$branch-$date" or something like that. > > There's a fairly extensive test suite. This might be > an option. > > > Remember: you don't have to tag the top-of branch. You > can tag any commit, > > after-the-fact. So even if you've done other > development since, just make > > sure to tag the commit you actually built and tested. > > Good point. I think I've got enough information to > get something > working. Thanks for all the help. > > Chris > -- > To unsubscribe from this list: send the line "unsubscribe > git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >