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

Re: [PATCH 1/2] Add feature release instructions to MaintNotes addendum

From
RGRaman Gupta <rocketraman@fastmail.fm>
Date
Mar 26, 2009, 13:51 UTC
Message-ID
<49CB8871.2020605@fastmail.fm>
In-Reply-To
<20090326121017.6117@nanako3.lavabit.com>
Nanako Shiraishi wrote:
Show 13 quoted lines
> Quoting rocketraman@fastmail.fm:
> 
>> + - The 'maint' branch is updated to the new release.
>> +
>> +     $ git checkout maint
>> +     $ git merge master
>> +
>> +   This is equivalent to deleting maint and recreating it from
>> +   master, but it preserves the maint reflog.
> 
> After giving a recipe that is better than an alternative, what's
> the point of describing an inferior alternative as "equivalent",
> when it is obviously not "equivalent"?
Is this better:

The resulting maint tree is equivalent to deleting maint and recreating it from the tip of master, but merging from master preserves the maint reflog.

Cheers, Raman

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