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

Re: Groups of commits

From
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 28, 2010, 12:46 UTC
Message-ID
<i2k32541b131004280546j5fc4e160oa1618fe14d83a291@mail.gmail.com>
In-Reply-To
<y2t81b0412b1004280105p46962bdeq163bc4fb92cb0fdb@mail.gmail.com>
On Wed, Apr 28, 2010 at 4:05 AM, Alex Riesen <raa.lkml@gmail.com> wrote:
Show 9 quoted lines
> On Wed, Apr 28, 2010 at 07:25, Tay Ray Chuan <rctay89@gmail.com> wrote:
>> Just to add to the "merge in topic branches" idea - if you find that
>> the commits are trivially fast-forwardable, you can still add a short
>> note/cover letter with
>>
>>  git merge --no-ff -m "Added in foo's work" <branch/commit>
>
> Except that is not a "short note" anymore, but a full-fledged merge
> commit. You forced it with "--no-ff".

I think it's safe to say that a commit *is* just a "short note" about a tree, who made it, the reason (message), and who its parents were.

Have fun,
Avery
Previous: Alex Riesen
Message 6 of 6 in “Groups of commits”
  1. John TapsellApr 28, 2010
  2. Jeff KingApr 28, 2010
  3. Michael PooleApr 28, 2010
  4. Tay Ray ChuanApr 28, 2010
  5. Alex RiesenApr 28, 2010
  6. Avery PennarunApr 28, 2010

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.