git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raman Gupta <rocketraman@fastmail.fm>
To: Thiago Farina <tfransosi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCHv2] Update gitworkflows man page to include release 	workflow
Date: Wed, 11 Nov 2009 10:23:26 -0500	[thread overview]
Message-ID: <4AFAD6EE.3010205@fastmail.fm> (raw)
In-Reply-To: <a4c8a6d00911110505m2f21a787sfb3e0d6c130b0b4d@mail.gmail.com>

Thiago Farina wrote:
> Hi,
> 
> On Tue, Nov 10, 2009 at 2:08 PM,  <rocketraman@fastmail.fm> wrote:
>> From: Raman Gupta <raman@rocketraman.com>
>>
>> The gitworkflows man page currently provides an overview of the workflows
>> used by git.git itself to serve as inspiration for people to use when
>> designing their own workflows. The current man page does a reasonable
>> job at describing the development process, but it does not contain any
>> guidance as to the workflow used for releases. Now add a basic
>> introduction to the branch management required for a release, so that a
>> reader may understand how the maint, master, next, and topic branches are
>> affected.
> Here
> http://git.kernel.org/?p=git/git.git;a=blob;f=Checklist.txt;h=37745f39487537117fb7f3a9a6f5b8e7d989a884;hb=refs/heads/todo
> there is a release checklist, maybe you could extend your patch to
> include more information from this?

Most of the checklist is specific to the git infrastructure rather
than git branch management. The latter is the focus of the
gitworkflows man page. The relevant items from checklist.txt (e.g.
merge 'maint' to 'master') are already included in the patch.

Cheers,
Raman

  reply	other threads:[~2009-11-11 15:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 16:08 Update gitworkflows man page to include release workflow rocketraman
2009-11-10 16:08 ` [PATCHv2] " rocketraman
2009-11-10 18:06   ` Štěpán Němec
2009-11-10 18:10     ` Raman Gupta
2009-11-11 13:05   ` Thiago Farina
2009-11-11 15:23     ` Raman Gupta [this message]
2009-11-11 19:43   ` Junio C Hamano
2009-11-12  0:32     ` Raman Gupta
2009-11-12  8:03       ` Junio C Hamano
2009-11-12  8:10       ` Thomas Rast
2009-11-12 16:54         ` Raman Gupta
2009-11-11 20:41   ` Thomas Rast
2009-11-12  8:27   ` Thomas Rast

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=4AFAD6EE.3010205@fastmail.fm \
    --to=rocketraman@fastmail.fm \
    --cc=git@vger.kernel.org \
    --cc=tfransosi@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.
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).