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
Apr 1, 2009, 16:15 UTC
Message-ID
<7vtz581hbn.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<49D1120B.8060601@fastmail.fm>
Raman Gupta <rocketraman@fastmail.fm> writes:
Show 6 quoted lines
> It might be useful to add some explanation of why one would want to
> rewind and rebuild vs simply continue as is.
>
> I guess the advantage is that the history for next starts out nice and
> clean for the next release, without any cruft from repeated merging of
> topic branches.

Repeated merges are usually not a major issue. Summarization tools such as log and shortlog can be told not to list merges.

What matters more is a revert of a topic, that looked promising when it started, but later found undesirable or premature. In such a case, the topic is reverted out of 'next' and but the fact remains in the history that it was once merged, and it was reverted. We would want to get rid of these records at some point to give a chance for another incarnation of the topic done right a clean slate to retry, and a feature release is a good point in history to do so.

> The disadvantage is that one must publish the operation and all forks
> must deal with the rebase.
Yes.
Previous: Raman GuptaNext: Junio C Hamano
Message 7 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.