Hi, the patches for rebase-i migration follow. Why this intermediate mail? Because the patches will not apply to master/next/pu/whatever. It needs js/rebase-i-sequencer, that is "dropped for now" from git.git. So you have to do some extra work to apply. Well, I could've just added a "Squashed js/rebase-i-sequencer patch" or something, but 1. I didn't write the patches so I don't want to claim I'm the author, 2. It's an opportunity to try sequencer, as follows: If you still have the commits (a freshly cloned repo hasn't), you can do: git sequencer <<EOF #pick 367bcc9cbc3d903c076f # optional: "fake-editor: output TODO list if unchanged" pick 0fa413ebc6e073a52d88 pick -R 88b1f0b8094638b1f953 # just to prevent a silly conflict pick 966fdf0ab272a64250fb pick 45d6022d611fd86a13c5 pick 051e0cfb88cd1d2a24bd # note: the following patches will make t3404 fail until migration to sequencer pick d9711a80796fd00169ca pick 10046a6f8adaccac0ea1 pick abe32eafcd8302c387ed pick d481bcc93f393bbfaaef pick dbcd70439f697deeb317 pick b1ba88d812434a51889f pick cc76fdac36ff25eaa77b pick f8e037d76a224bd87236 pick 777790a3bdfeb91ee4a6 pick 7cdf70106412f44b9116 pick 14a4f1e0a804ccc905d7 EOF If this results in a lot of "is not a commit" errors, then do git sequencer --abort (You may also have a look at git sequencer --status, if you like) and fetch the missing commits: git fetch git://repo.or.cz/git/sbeyer.git seq-proto-dev2 and then redo the example above. When the patches are applied, the following patches will apply, too. Regards, Stephan PS: Sorry, for the nastiness of the patch application ;-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
