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

Re: [PATCH] Better advice on using topic branches for kernel development

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 21, 2010, 16:32 UTC
Message-ID
<20101021163208.GC3732@burratino>
In-Reply-To
<4cc06a8128436b591e@agluck-desktop.sc.intel.com>
Hi Tony,
Luck, Tony wrote:
Show 5 quoted lines
> Maybe they do this because they read it in the Git user-manual.
> 
> Fix the manual to give them better guidance.
> 
> Signed-off-by: Tony Luck <tony.luck@intel.com>
[...]
> Originally posted on October 1st ... no comments received.

No comments received, but applied to "maint". Sorry for the confusion.

Occasionally there has been discussion of automating notification that a patch was applied. Maybe someone on the git@ list might consider it worth trying (or maybe not).

Thanks.
Previous: Luck, Tony
Message 2 of 2 in “Better advice on using topic branches for kernel development”
  1. Better advice on using topic branches for kernel developmentLuck, Tony, Oct 21, 2010
  2. Jonathan NiederOct 21, 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.