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

Re: [PATCH 2/2] Add feature release instructions to gitworkflows man page

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 30, 2009, 06:57 UTC
Message-ID
<7vk567ijlf.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1238391319-4953-2-git-send-email-rocketraman@fastmail.fm>
rocketraman@fastmail.fm writes:
> From: Raman Gupta <raman@rocketraman.com>
>
> Based on a mailing list discussion, add a description of the workflow,
> and associated commands, for creating a feature release.

The same comment applies to the other one, but this commit log message is really lacking. If you do not bother to summarize the discussion, place a pointer to the list archive, and more importantly, please describe *why* this change is desiable.

I am not sure rewinding and rebuilding of 'next', or even having 'next', is applicable for other projects as a BCP. Other parts (except for the "branch -f" bit I've already told you about in the other message) looked good.

Thanks.
Previous: rocketraman@fastmail.fmNext: Raman Gupta
Message 3 of 9 in “Add feature release instructions to MaintNotes addendum”
  1. 1/2 Add feature release instructions to MaintNotes addendumrocketraman@fastmail.fm, Mar 30, 2009
  2. 2/2 Add feature release instructions to gitworkflows man pagerocketraman@fastmail.fm, Mar 30, 2009
  3. Junio C HamanoMar 30, 2009
  4. Raman GuptaMar 30, 2009
  5. Junio C HamanoMar 30, 2009
  6. Raman GuptaMar 30, 2009
  7. Junio C HamanoApr 1, 2009
  8. Junio C HamanoMar 30, 2009
  9. Raman GuptaMar 30, 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.