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

Re: [RFC] Patches exchange is bad?

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Aug 17, 2005, 09:07 UTC
Message-ID
<46a038f90508170207578b1c0@mail.gmail.com>
In-Reply-To
<20050817082709.28135.qmail@web26301.mail.ukl.yahoo.com>
On 8/17/05, Marco Costalba <mcostalba@yahoo.it> wrote:
> Of course I can feed proper subject and description to git-commit but I would like
> to find something less intrusive

I don't know if it helps, but I think that StGIT is what you are looking for, not only because you have more tools to deal with patches, but also because patches that are in the 'stack' are actually really malleable. You can edit and reedit the patch w its commit msg and all, commit it to the stack, and reedit it again later. It only becomes immutable when you commit to the underlying git repo.

cheers,
martin
Previous: Marco Costalba
Message 2 of 2 in “Re: [RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 17, 2005
  2. Martin LanghoffAug 17, 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.