From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Sean Kelley <sean.v.kelley@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GIT - releases workflow
Date: Tue, 12 Dec 2006 23:54:14 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0612122353320.2807@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <89b129c60612121444t18ba94ecv57eea4c72be1663a@mail.gmail.com>
Hi,
On Tue, 12 Dec 2006, Sean Kelley wrote:
> I was wondering if anyone could share ideas on how best to use GIT to
> handle releases for those working with a remote GIT repository? Do you
> create a branch and push it to the remote? Thus you have a new branch
> referencing the particular release?
Why not just tag the release, and push the tag?
Hth,
Dscho
next prev parent reply other threads:[~2006-12-12 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 22:44 GIT - releases workflow Sean Kelley
2006-12-12 22:54 ` Johannes Schindelin [this message]
2006-12-13 9:10 ` Matthias Kestenholz
2006-12-13 10:36 ` Johannes Schindelin
2006-12-13 10:56 ` Shawn Pearce
2006-12-13 11:14 ` Shawn Pearce
2006-12-13 12:34 ` Sean Kelley
2006-12-13 12:39 ` Sean Kelley
2006-12-13 13:13 ` Andreas Ericsson
2006-12-13 2:43 ` Linus Torvalds
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0612122353320.2807@wbgn013.biozentrum.uni-wuerzburg.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sean.v.kelley@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).