git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv2] Update gitworkflows man page to include release workflow

From
Thiago Farina <tfransosi@gmail.com>
Date
Nov 11, 2009, 13:05 UTC
Message-ID
<a4c8a6d00911110505m2f21a787sfb3e0d6c130b0b4d@mail.gmail.com>
In-Reply-To
<1257869339-15999-2-git-send-email-rocketraman@fastmail.fm>
Hi,
On Tue, Nov 10, 2009 at 2:08 PM,  <rocketraman@fastmail.fm> wrote:
Show 10 quoted lines
> 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?

Previous: Raman GuptaNext: Raman Gupta
Message 5 of 13 in “Update gitworkflows man page to include release workflow”
  1. rocketraman@fastmail.fmNov 10, 2009
  2. [PATCHv2] Update gitworkflows man page to include release workflowrocketraman@fastmail.fm, Nov 10, 2009
  3. Štěpán NěmecNov 10, 2009
  4. Raman GuptaNov 10, 2009
  5. Thiago FarinaNov 11, 2009
  6. Raman GuptaNov 11, 2009
  7. Junio C HamanoNov 11, 2009
  8. Raman GuptaNov 12, 2009
  9. Junio C HamanoNov 12, 2009
  10. Thomas RastNov 12, 2009
  11. Raman GuptaNov 12, 2009
  12. Thomas RastNov 11, 2009
  13. Thomas RastNov 12, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.