From: Asaf <asafs2000@yahoo.com>
To: git@vger.kernel.org
Subject: Tagging stable releases
Date: Tue, 14 Apr 2009 11:43:55 -0700 (PDT) [thread overview]
Message-ID: <23045562.post@talk.nabble.com> (raw)
Hello,
I'm creating many branches, checkout code, make changes, etc..
At the end, I always merge these branches to the master branch and delete
them when I finish,
At the point where my local master repo seems to be stable, I push the
changes to an origin repo that is public.
I guess this is a standard cycle, right?
What I'm confused about is how to tag correctly versions that are stable,
Should I locally just add a tag and push the tag to the public repo?
Is it enough to use a lightweight tagging for tagging a certain commit as a
release?
Is it possible later on to checkout a tag, make a change and push the change
into the tagged version?
Many thanks,
Asaf.
--
View this message in context: http://www.nabble.com/Tagging-stable-releases-tp23045562p23045562.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2009-04-14 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 18:43 Asaf [this message]
2009-04-15 8:33 ` Tagging stable releases Andreas Ericsson
2009-04-15 16:15 ` Stefan Näwe
2009-04-15 18:03 ` Andreas Ericsson
2009-10-28 12:17 ` Tim Mazid
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=23045562.post@talk.nabble.com \
--to=asafs2000@yahoo.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;
as well as URLs for NNTP newsgroup(s).