From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Brandon Casey <casey@nrlssc.navy.mil>, git@vger.kernel.org
Subject: Re: any way to apply tag across all branches in repository?
Date: Tue, 19 May 2009 14:06:39 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905191403090.3301@localhost.localdomain> (raw)
In-Reply-To: <4A131D16.1030001@nortel.com>
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.
Remember: you don't have to tag whatever is the "top" - tagging can happen
later. Tagging at build-time is perfectly fine.
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.
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.
Linus
next prev parent reply other threads:[~2009-05-19 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 16:26 any way to apply tag across all branches in repository? Chris Friesen
2009-05-19 16:52 ` Tomas Carnecky
2009-05-19 16:59 ` Chris Friesen
2009-05-19 17:05 ` Brandon Casey
2009-05-19 17:48 ` Chris Friesen
2009-05-19 18:33 ` Linus Torvalds
2009-05-19 19:05 ` Chris Friesen
2009-05-19 20:14 ` Linus Torvalds
2009-05-19 20:56 ` Chris Friesen
2009-05-19 21:06 ` Linus Torvalds [this message]
2009-05-19 21:31 ` Chris Friesen
2009-05-19 18:36 ` Brandon Casey
2009-05-19 19:05 ` Chris Friesen
2009-05-19 19:30 ` Brandon Casey
2009-05-19 19:49 ` Chris Friesen
2009-05-19 19:58 ` Brandon Casey
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 8:58 Mark Struberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.01.0905191403090.3301@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=casey@nrlssc.navy.mil \
--cc=cfriesen@nortel.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox