Re: any way to apply tag across all branches in repository?

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:

Von: Chris Friesen [off-list ref]
Betreff: Re: any way to apply tag across all branches in repository?
An: "Linus Torvalds" [off-list ref]
CC: "Brandon Casey" <redacted>, git@vger.kernel.org
Datum: Dienstag, 19. Mai 2009, 23:31
Linus Torvalds wrote:

quoted

On Tue, 19 May 2009, Chris Friesen wrote:

quoted

The tagging would be done only by the "official"

build process (which

quoted

quoted

pulls from an "official" repository), not by each

designer.  Typically

quoted

quoted

the official builds would be done weekly, more

frequently if requested.

quoted

Well, you can tag when you do that official build. Do

you really do 

quoted

"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.

quoted

Remember: you don't have to tag whatever is the "top"

- tagging can happen 

quoted

later. Tagging at build-time is perfectly fine.

Tagging at build-time is actually the plan.

quoted

In fact, I'd suggest going even further. Don't tag the

source branch when 

quoted

you build - tag it after it has passed whatever

testing you do (I hope you 

quoted

_do_ have some extensive test-suite before release),

and as you actually 

quoted

make it public (or whatever you do). Only at _that_

point, tag the tree 

quoted

with "release-$branch-$date" or something like that.

There's a fairly extensive test suite.  This might be
an option.

quoted

Remember: you don't have to tag the top-of branch. You

can tag any commit, 

quoted

after-the-fact. So even if you've done other

development since, just make 

quoted

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