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, 18:14 UTC
Message-ID
<7vljqmdgj0.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<49D10875.2060008@fastmail.fm>
Raman Gupta <rocketraman@fastmail.fm> writes:
Show 6 quoted lines
> Junio C Hamano wrote:
> ...
> If you wish to remove discussion of 'next' from this document, that is
> probably better done in a separate followup change. Though personally
> I think its a useful concept for readers to learn about as they are
> setting up their own workflows.
I do not have a particularly strong feeling about 'next' either way.

As the document states at the top, it lists ingredients from git.git management and it is left up to the readers to adopt parts that suit their needs, while not using others. In that spirit, the description of 'next' as "ahead of master that is supposed to be rock solid" may be a good thing to keep. It is orthogonal if the project wants to rewind and rebuild 'next' after every feature release---they do not need to (and we didn't do so for quite some time). One valid choice by readers is to adopt the concept of 'next' in their project but never rewind and rebuild it, and you made that clear that it is optional. So I think this part of your patch is good as-is.

Show 7 quoted lines
>> Other parts (except for the "branch -f" bit I've already told you
>> about in the other message) looked good.
>
> I'll add some discussion about the branch -f bit -- I hope you agree
> that in this document that is distributed with git, some
> beginner-level explanation of the difference between the branch -f and
> the merge approach is warranted?
Surely and thanks.
Previous: Raman GuptaNext: Raman Gupta
Message 5 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.