All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
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:56:54 -0600	[thread overview]
Message-ID: <4A131D16.1030001@nortel.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0905191307320.3301@localhost.localdomain>

Linus Torvalds wrote:
> On Tue, 19 May 2009, Chris Friesen wrote:

>> The brute-force way to do this would be to manually loop through each branch
>> and create a tag of the form "$branch_$version" to ensure unique tags.  But I was
>> hoping there was a more elegant way.
> 
> Well, I would suggest that you do it fundamentally differently.
> 
> Instead of tagging each build, I would suggest just associating each build 
> with the commit SHA1 of the time. That's what Linux does (if you enable 
> CONFIG_LOCALVERSION_AUTO), and it's _way_ superior to lots of crazy tags.
> 
> So for example, I can do
> 
> 	[torvalds@nehalem ~]$ uname -r
> 	2.6.30-rc6-00302-g72357d5-dirty
> 
> and it tells me exactly what kernel version I'm running (well, the "dirty"
> part means that it's not exact and has some additional patches that 
> weren't committed, but that's as close as you can get). It's very useful.

Agreed.  The project in question actually involves (among other things)
a linux kernel build, so we will be making use of this to work backwards
from the running kernel to the commit used to generate it.

However, we also want to be able to work in the other direction--given a
known-buggy kernel commit, which shipped versions of the product contain
the buggy code?  We do in-the-field upgrades, and different sites may be
running different versions, so it's important to be able to easily
determine which sites are currently running the buggy code so that we
can get them upgraded.  We know which sites are running which versions,
so it is useful to tag the repository branches with that version number.

> Trust me, something like the above is _much_ better than tagging each 
> branchthat you build. Partly because it means that you can do the builds 
> in a distributed manner, and they'll all get the version built in, rather 
> than having to rely on everybody tagging everything and then trying to 
> match up the tag to some random binary.

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.

Chris

  reply	other threads:[~2009-05-19 20:57 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 [this message]
2009-05-19 21:06             ` Linus Torvalds
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=4A131D16.1030001@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.