# Re: An alternate model for preparing partial commits

2 messages from 2008-06-28 to 2008-06-28. Participants: Theodore Tso, Miklos Vajna.
Thread: https://gitlist.dev/t/14196

## Theodore Tso, 2008-06-28 01:17

Subject: Re: An alternate model for preparing partial commits
Message-ID: <20080628011723.GB15463@mit.edu>
URL: https://gitlist.dev/e/20080628011723.GB15463%40mit.edu

```
On Fri, Jun 27, 2008 at 08:29:15PM -0000, David Jeske wrote:
> 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

```

## Miklos Vajna, 2008-06-28 01:56

Subject: Re: An alternate model for preparing partial commits
Message-ID: <20080628015608.GF2058@genesis.frugalware.org>
URL: https://gitlist.dev/e/20080628015608.GF2058%40genesis.frugalware.org
In-Reply-To: <20080628011723.GB15463@mit.edu>

```
On Fri, Jun 27, 2008 at 09:17:24PM -0400, Theodore Tso <tytso@mit.edu> wrote:
> Splitting patches is harder to do and probably is one of the things
> you have to do manually.

Or not that hard:

http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/git-rebase.txt;hb=HEAD#l363

:-)

```