git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] minor git-jump improvements
Date: Sun, 24 Jul 2016 11:32:51 -0400	[thread overview]
Message-ID: <20160724153251.GA32609@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1607231050360.14111@virtualbox>

On Sat, Jul 23, 2016 at 10:52:09AM +0200, Johannes Schindelin wrote:

> On Fri, 22 Jul 2016, Jeff King wrote:
> 
> > Here are a few quick fixes and features for git-jump. The first is a bug
> > I noticed and fixed recently. And that reminded me of the second one,
> > which I'd been carrying in my local copy for a long time.
> > 
> >   [1/3]: contrib/git-jump: fix greedy regex when matching hunks
> >   [2/3]: contrib/git-jump: add whitespace-checking mode
> >   [3/3]: contrib/git-jump: fix typo in README
> 
> These 3 patches look good to me.
> 
> They also made me aware of git-jump's existence and purpose. I think I
> shall use this script a lot myself from now on.

Yay, now there are at least 2 users.

Bug reports and patches very welcome. :)

-Peff

      reply	other threads:[~2016-07-24 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 16:27 [PATCH 0/3] minor git-jump improvements Jeff King
2016-07-22 16:28 ` [PATCH 1/3] contrib/git-jump: fix greedy regex when matching hunks Jeff King
2016-07-22 16:29 ` [PATCH 2/3] contrib/git-jump: add whitespace-checking mode Jeff King
2016-07-22 16:35   ` [PATCH v2 " Jeff King
2016-07-22 16:30 ` [PATCH 3/3] contrib/git-jump: fix typo in README Jeff King
2016-07-23  8:52 ` [PATCH 0/3] minor git-jump improvements Johannes Schindelin
2016-07-24 15:32   ` Jeff King [this message]

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=20160724153251.GA32609@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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.
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).