From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: David <bouncingcats@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: "Give me a break"... well, you gave me one
Date: Mon, 1 Apr 2019 17:26:43 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1904011724550.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAMPXz=qa5GA6zynpPWTDpKeh0J=p2y31xA7gwk5Y7swF2z1OHQ@mail.gmail.com>
Hi David,
On Sat, 30 Mar 2019, David wrote:
> On Thu, 7 Mar 2019 at 09:00, Mike Hommey <mh@glandium.org> wrote:
> > On Wed, Mar 06, 2019 at 03:14:11PM +0100, Johannes Schindelin wrote:
> > >
> > > just wanted to express my gratitude for your idea to introduce the `break`
> > > command in `git rebase -i`'s todo list. I use it *all* the time now.
> >
> > +1. Before that, I was using `x bash`, and ended up doing `git rebase
> > --continue` in that shell in many cases, which didn't end up so well
>
> 'x bash' will start another shell, that seems an odd thing to do.
Indeed, but it used to work quite well for me, too. I usually made extra
sure to start a new session by using `exec bash -i`...
> I have been using 'x false' to generate an error exit status to interrupt
> the rebase and drop into the current shell. Then 'git rebase --continue'
> to resume.
That's not so scriptable. I have a couple of scripts around the
interactive rebase.
Besides, `b` is much shorter to type than `x false` (and I also cannot
tyop it late at night as `x flase`, although that would have the same
effect, I guess, of stopping the interactive rebase).
Ciao,
Johannes
next prev parent reply other threads:[~2019-04-01 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 14:14 "Give me a break"... well, you gave me one Johannes Schindelin
2019-03-06 21:30 ` Mike Hommey
2019-03-29 23:49 ` David
2019-04-01 15:26 ` Johannes Schindelin [this message]
2019-03-29 22:34 ` Stefan Beller
2019-04-01 15:24 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1904011724550.41@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=bouncingcats@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).