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

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

From
Thomas Rast <trast@student.ethz.ch>
Date
Nov 11, 2009, 20:41 UTC
Message-ID
<200911112142.00209.trast@student.ethz.ch>
In-Reply-To
<1257869339-15999-2-git-send-email-rocketraman@fastmail.fm>

It's nice to see someone work on this manpage :-) I sadly do not have the time to read the whole patch right now, though I'll try and catch up tomorrow or so. In the meantime I do have one remark:

rocketraman@fastmail.fm wrote:
Show 6 quoted lines
> +The maintainer may use the following release workflow:
> +
> +He first tags the tip of 'master' with a release tag, then he updates
> +the 'maint' branch to the current tip of 'master' for managing future
> +maintenance fixes on the current release, and lastly he optionally
> +rebuilds 'next' from the tip of 'master'.
The current gitworkflows is mostly formulated in the imperative, as in
  To test the interaction of several topics, merge them into a
  throw-away branch.  You must never base any work on such a branch!
or by directly describing the tools in the third person, as in
  * linkgit:git-push[1] copies your branches to a remote repository,
    usually to one that can be read by all involved parties;

It would certainly be nice to be somewhat consistent. Since at first glance your description is aimed at the maintainer himself, I assume that would mostly mean addressing the maintainer as "you", and formulating the rules in the imperative.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Raman GuptaNext: Thomas Rast
Message 12 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.