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

Re: replacing a bad commit

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 5, 2007, 20:58 UTC
Message-ID
<20070205205853.GA8908@spearce.org>
In-Reply-To
<20070205205324.GC21890@daga.cl>
Blu Corater <blu@daga.cl> wrote:
> Let me learn the list conventions on sending patches and I will send
> something.
Its covered in Documentation/SubmittingPatches.
Any patches to improve Git are definately welcome.  Please help.  ;-)
-- 
Shawn.
Previous: Blu Corater
Message 8 of 8 in “replacing a bad commit”
  1. Blu CoraterFeb 5, 2007
  2. Jakub NarebskiFeb 5, 2007
  3. Blu CoraterFeb 5, 2007
  4. Shawn O. PearceFeb 5, 2007
  5. Blu CoraterFeb 5, 2007
  6. Jakub NarebskiFeb 5, 2007
  7. Blu CoraterFeb 5, 2007
  8. Shawn O. PearceFeb 5, 2007

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.