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 13:05:49 -0600 [thread overview]
Message-ID: <4A13030D.8000000@nortel.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0905191132490.3301@localhost.localdomain>
Linus Torvalds wrote:
>
> On Tue, 19 May 2009, Chris Friesen wrote:
>> However, if I make a change on the arch-specific branch, then tag the
>> main branch and merge it into the arch-specific branch, git tells me
>> the arch-specific branch is already up-to-date and the tag doesn't
>> get propagated.
>
> You can always just do "git fetch --tags" to fetch any new tags without
> doing anything else.
This is all in the same local repository, but with target-specific branches
containing arch-specific changes on top of a common codebase. The
arch-specific stuff often comes from board vendors and such, and they're
never going to be merged back into the common codebase.
I'm looking for some way to conceptually tag the current head of each
branch to indicate "this commit was used to build product version FOO" so
that later on when we find a bug in our code we can tell which product
version(s) contain the bug and need to be patched in the field.
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.
Chris
next prev parent reply other threads:[~2009-05-19 19:06 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 [this message]
2009-05-19 20:14 ` Linus Torvalds
2009-05-19 20:56 ` Chris Friesen
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=4A13030D.8000000@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.