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

Re: An alternate model for preparing partial commits

From
Theodore Tso <tytso@mit.edu>
Date
Jun 28, 2008, 01:17 UTC
Message-ID
<20080628011723.GB15463@mit.edu>
On Fri, Jun 27, 2008 at 08:29:15PM -0000, David Jeske wrote:
Show 12 quoted lines
> git has all the concepts I want except one. However, it makes the process
> pretty manual. Here is an idea about automating it. I'll talk about that one
> new concept at the bottom.
> 
> I think of this as reorder/merge/split...
> 
> reorder: Picture that a list of commits on this branch opens in an
> editor. You are free to rearrange the lines in any order you want,
> but you have to keep all the lines. When you are done reordering the
> lines, the tool creates a new topic branch and applies the changes
> (probably with cherrypick) to the new topic branch. If there are no
> conflicts, you're done.....

Read the man page for for "git rebase --interactive". I think you will find that it handles reording and merging (its called squashing) already.

Splitting patches is harder to do and probably is one of the things you have to do manually.

						- Ted
Next: Miklos Vajna
Message 1 of 2 in “Re: An alternate model for preparing partial commits”
  1. Theodore TsoJun 28, 2008
  2. Miklos VajnaJun 28, 2008

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.