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

Re: Recommended work flow with git to send in patches

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jul 27, 2010, 15:39 UTC
Message-ID
<20100727153901.GA5351@kytes>
In-Reply-To
<AANLkTiksAOpFG3vGVGcbeZ0NcpQ5FbDjnZ7yDxUsAY_r@mail.gmail.com>
Hi Tong,
Tong Sun writes:
> Compressing my "life long story" into a single question -- what's the
> recommended work flow to work with git and send in patches, when
> upstream might be slow in respond, and require squashing relevant
> patches into one?

Personally, I use `git symbolic-ref` to create a new branch without history, stage and create commits to send off to the list from there; it's also worth noting that I keep the branch to fixup my commits and re-roll after reviews.

-- Ram
Previous: Tong SunNext: Tong Sun
Message 4 of 14 in “Recommended work flow with git to send in patches”
  1. Tong SunJul 27, 2010
  2. Ævar Arnfjörð BjarmasonJul 27, 2010
  3. Tong SunJul 27, 2010
  4. Ramkumar RamachandraJul 27, 2010
  5. Tong SunJul 27, 2010
  6. Ramkumar RamachandraJul 27, 2010
  7. Jakub NarebskiJul 27, 2010
  8. Ramkumar RamachandraJul 27, 2010
  9. Jakub NarebskiJul 27, 2010
  10. Tong SunJul 27, 2010
  11. Jakub NarebskiJul 28, 2010
  12. Tong SunJul 28, 2010
  13. Jakub NarebskiJul 28, 2010
  14. Tong SunJul 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.