From: Jeff Epler <jepler@unpythonic.net>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [RFC PATCH] git-gui: Allow staging multiple lines at once
Date: Thu, 22 Oct 2009 20:53:15 -0500 [thread overview]
Message-ID: <20091023015315.GB10347@unpythonic.net> (raw)
In-Reply-To: <20091022195116.GB3944@book.hvoigt.net>
On Thu, Oct 22, 2009 at 09:51:16PM +0200, Heiko Voigt wrote:
> Tested it and it works like a charm. I will include Shawn in the CC: so
> he can comment.
Thanks, but don't miss the v2 patch:
http://thread.gmane.org/gmane.comp.version-control.git/130968
this fixes a bug staging line(s) followed only by deletions.
Jeff
prev parent reply other threads:[~2009-10-23 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 19:54 [RFC PATCH] git-gui: Allow staging multiple lines at once Jeff Epler
2009-10-19 20:08 ` Geert Bosch
2009-10-20 6:11 ` Johannes Sixt
2009-10-20 17:09 ` Dirk Süsserott
2009-10-22 19:51 ` Heiko Voigt
2009-10-23 1:53 ` Jeff Epler [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=20091023015315.GB10347@unpythonic.net \
--to=jepler@unpythonic.net \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=spearce@spearce.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).