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

Lump commit HOWTO?

From
JBJosh Boyer <jwboyer@gmail.com>
Date
Jul 13, 2007, 01:21 UTC
Message-ID
<625fc13d0707121821l70e2d6aaw555c79b5d700585f@mail.gmail.com>
Hi All,

I have a specific workflow in mind that I'm not entirely sure how to accomplish with git. What I'd like to do is track a project in a local branch, and do commits of my own there as well. Then when I'm ready to submit the work, I want to take all the incremental commits and lump them into a single new commit and push that out as a patch or into a branch for people to pull from.

E.g.
1) clone upstream into foo branch
2) commit A
3) commit B
4) pull upstream changes into foo branch
5) commit C
6) commit D
7) repeat steps 2 - 6 in various orders
8) take all local commits (A - D) and create a single commit without
any of the upstream changes in it

Is something like that easily accomplished? Or perhaps a different workflow that would allow similar results?

josh
Next: Alex Riesen
Message 1 of 4 in “Lump commit HOWTO?”
  1. Josh BoyerJul 13, 2007
  2. Alex RiesenJul 13, 2007
  3. Josh BoyerJul 13, 2007
  4. martin f krafftJul 13, 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.