From: "Chris Friesen" <cfriesen@nortel.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: any way to apply tag across all branches in repository?
Date: Tue, 19 May 2009 11:48:29 -0600 [thread overview]
Message-ID: <4A12F0ED.4070707@nortel.com> (raw)
In-Reply-To: <Y0WmOpNg_9ptwbJ3VHYrzAgFtDvPi5pn4Tz-0w5Phhlo9frjieUaeA@cipher.nrlssc.navy.mil>
Brandon Casey wrote:
> If I understand you correctly, you are doing your primary development on
> the "main" branch and then merging this into the architecture specific
> branches which contain additional architecture specific changes.
Correct.
> All you need to do is tag the "main" branch. Actually, you are tagging
> the commit that the branch currently points at. When this branch is
> merged into the other branches, they will also contain this commit, and
> 'git describe' will use the tag you created when generating the version
> string.
I think this would work if the most recent commit is on the main branch.
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.
Chris
next prev parent reply other threads:[~2009-05-19 17:48 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 [this message]
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
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=4A12F0ED.4070707@nortel.com \
--to=cfriesen@nortel.com \
--cc=casey@nrlssc.navy.mil \
--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 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.