Re: RFC: new git-splice subcommand for non-interactive branch splicing

2016-05-28 Thread Adam Spiers
On Sat, May 28, 2016 at 09:06:59AM +0200, Johannes Schindelin wrote: > Hi Adam, > > please reply-to-all on this list. Sorry, I forgot that was the policy here. Every list and individual has different preferences on whether to Cc: on list mail, so I find it almost impossible to keep track of who

Re: RFC: new git-splice subcommand for non-interactive branch splicing

2016-05-28 Thread Johannes Schindelin
Hi Adam, please reply-to-all on this list. On Fri, 27 May 2016, Adam Spiers wrote: > My feeling is that rebase -i provides something tremendously > important, which the vast majority of users use on a regular basis, > but that git is currently missing a convenient way to > *non-interactively* pe

Re: RFC: new git-splice subcommand for non-interactive branch splicing

2016-05-27 Thread Adam Spiers
Hi Johannes, Thanks for the quick reply! Responses inline below: On Fri, May 27, 2016 at 05:27:14PM +0200, Johannes Schindelin wrote: > On Fri, 27 May 2016, Adam Spiers wrote: > > > Description > > --- > > > > git-splice(1) non-interactively splices the current branch by removing > > a

Re: RFC: new git-splice subcommand for non-interactive branch splicing

2016-05-27 Thread Johannes Schindelin
Hi Adam, On Fri, 27 May 2016, Adam Spiers wrote: > Description > --- > > git-splice(1) non-interactively splices the current branch by removing > a range of commits from within it and/or cherry-picking a range of > commits into it. It's essentially just a glorified wrapper around > cher

RFC: new git-splice subcommand for non-interactive branch splicing

2016-05-27 Thread Adam Spiers
Hi all, I finally got around to implementing a new git subcommand which I've wanted for quite a while. I've called it git-splice. Description --- git-splice(1) non-interactively splices the current branch by removing a range of commits from within it and/or cherry-picking a range of com