From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/3] rebase -i: handle --continue more like non-interactive rebase
Date: Wed, 1 Aug 2007 23:45:56 +0200 [thread overview]
Message-ID: <20070801214556.GA2911@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0708011654510.14781@racer.site>
Johannes Schindelin, Wed, Aug 01, 2007 17:57:25 +0200:
> On Fri, 13 Jul 2007, Alex Riesen wrote:
> > Johannes Schindelin, Sun, Jul 08, 2007 04:01:29 +0200:
> > > Non-interactive rebase requires the working tree to be clean, but
> > > applies what is in the index without requiring the user to do it
> > > herself. Imitate that, but (since we are interactive, after all)
> > > fire up an editor with the commit message.
> >
> > Could we also have "git rebase <base> <branch>"?
>
> Don't we do that already? AFAICT it is already in the synopsis, ever
> since rebase -i was introduced into the "next" branch, on June 25...
>
Err... "git rebase -i <base> <branch>"
Does not work, just checked:
$ git rebase -i base branch
/usr/local/bin/git-rebase--interactive: 482: cannot create /home/user/projects/tmp/.git/.dotest-merge/output: Directory nonexistent
cat: /home/user/projects/tmp/.git/.dotest-merge/output: No such file or directory
Invalid branchname: branch
next prev parent reply other threads:[~2007-08-01 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 2:01 [PATCH 1/3] rebase -i: handle --continue more like non-interactive rebase Johannes Schindelin
2007-07-08 4:40 ` Johannes Schindelin
2007-07-12 22:26 ` Alex Riesen
2007-08-01 15:57 ` Johannes Schindelin
2007-08-01 21:45 ` Alex Riesen [this message]
2007-08-01 22:31 ` [PATCH] rebase -i: fix for optional [branch] parameter Johannes Schindelin
2007-08-01 22:32 ` [PATCH] Fix rebase interactive to allow specifying branch to rebase along with the base Alex Riesen
2007-08-01 22:36 ` Johannes Schindelin
2007-08-01 22:40 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070801214556.GA2911@steel.home \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).