From: "Sean Kelley" <sean.v.kelley@gmail.com>
To: git@vger.kernel.org
Subject: GIT - releases workflow
Date: Tue, 12 Dec 2006 16:44:23 -0600 [thread overview]
Message-ID: <89b129c60612121444t18ba94ecv57eea4c72be1663a@mail.gmail.com> (raw)
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?
Sean
--
next reply other threads:[~2006-12-12 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 22:44 Sean Kelley [this message]
2006-12-12 22:54 ` GIT - releases workflow Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89b129c60612121444t18ba94ecv57eea4c72be1663a@mail.gmail.com \
--to=sean.v.kelley@gmail.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 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.