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

Re: [PATCH 1/7] Using svn pools seems to solve the memory leak problem

From
Junio C Hamano <junkio@cox.net>
Date
Nov 2, 2005, 22:38 UTC
Message-ID
<7v64raptdq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<E1EXQWT-000504-Qw@localhost.localdomain>

I see you are resending the previous round after splitting, but could you be a bit more careful about the commit log? One liner title that is self-sufficient (as opposed to just the initial part of one sentence, cut off at whereever your editor happened to decide to fold line), which goes to Subject:, and the body of the message as a separate paragraph.

Especially something like this (5/7) does not make much sense:
    From: Yaacov Akiba Slama <ya@slamail.org>
    Subject: [PATCH 5/7] When copying files and/or directories from several branches in one single
    Date: Wed, 02 Nov 2005 23:51:57 +0200
    revision, all these branches are used as parents of the commit.
Previous: Yaacov Akiba Slama
Message 2 of 2 in “Using svn pools seems to solve the memory leak problem”
  1. 1/7 Using svn pools seems to solve the memory leak problemYaacov Akiba Slama, Nov 2, 2005
  2. Junio C HamanoNov 2, 2005

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.