{"thread":{"id":"19422","subject":"Re: any way to apply tag across all branches in repository?","startedAt":"2009-05-20T08:58:12Z","lastAt":"2009-05-20T08:58:12Z","messageCount":1,"participants":["Mark Struberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"114326","messageId":"627610.63870.qm@web27808.mail.ukl.yahoo.com","threadId":"19422","inReplyTo":null,"subject":"Re: any way to apply tag across all branches in repository?","fromName":"Mark Struberg","fromEmail":"struberg@yahoo.de","sentAt":"2009-05-20T08:58:12Z","receivedAt":"2009-05-20T08:58:12Z","isPatch":false,"sender":{"key":"struberg@yahoo.de","avatar":"https://gravatar.com/avatar/119742c3e8dbc8db35a92bdff0581aec8d364d415f770e60431cba262daa974f?d=mp&s=160"},"body":"\n> We have one \"official\" branch for each target board...so\n> maybe a dozen or so branches.\n\nChis, to me this sounds more like you abuse SCM branches for what should be into 'modules'\nIn SVN this would make not a big difference (because of the silly svn:copy thingy) but for any sane SCM, tags are not directories!\n\nIf you move all your board specific code into child-modules, then you could happily tag over your whole project (including all those modules).\n\nLieGrue,\nstrub\n\n--- Chris Friesen schrieb am Di, 19.5.2009:\n\n> Von: Chris Friesen \n> Betreff: Re: any way to apply tag across all branches in repository?\n> An: \"Linus Torvalds\" \n> CC: \"Brandon Casey\" , git@vger.kernel.org\n> Datum: Dienstag, 19. Mai 2009, 23:31\n> Linus Torvalds wrote:\n> > \n> > On Tue, 19 May 2009, Chris Friesen wrote:\n> >> The tagging would be done only by the \"official\"\n> build process (which\n> >> pulls from an \"official\" repository), not by each\n> designer.  Typically\n> >> the official builds would be done weekly, more\n> frequently if requested.\n> > \n> > Well, you can tag when you do that official build. Do\n> you really do \n> > \"official\" builds from all branches? That sounds a bit\n> insane.\n> \n> We have one \"official\" branch for each target board...so\n> maybe a dozen\n> or so branches.\n> \n> Developers do private builds, but they're not tagged.\n> \n> > Remember: you don't have to tag whatever is the \"top\"\n> - tagging can happen \n> > later. Tagging at build-time is perfectly fine.\n> \n> Tagging at build-time is actually the plan.\n> \n> > In fact, I'd suggest going even further. Don't tag the\n> source branch when \n> > you build - tag it after it has passed whatever\n> testing you do (I hope you \n> > _do_ have some extensive test-suite before release),\n> and as you actually \n> > make it public (or whatever you do). Only at _that_\n> point, tag the tree \n> > with \"release-$branch-$date\" or something like that.\n> \n> There's a fairly extensive test suite.  This might be\n> an option.\n> \n> > Remember: you don't have to tag the top-of branch. You\n> can tag any commit, \n> > after-the-fact. So even if you've done other\n> development since, just make \n> > sure to tag the commit you actually built and tested.\n> \n> Good point.  I think I've got enough information to\n> get something\n> working.  Thanks for all the help.\n> \n> Chris\n> --\n> To unsubscribe from this list: send the line \"unsubscribe\n> git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n> \n\n\n \n"}]}