From: "Shawn O. Pearce" <spearce@spearce.org>
To: jepler@unpythonic.net
Cc: git@vger.kernel.org, Heiko Voigt <hvoigt@hvoigt.net>,
Peter Baumann <waste.manager@gmx.de>
Subject: Re: [PATCH 2/2] Make it possible to apply a range of changes at once
Date: Sat, 23 Jan 2010 15:05:43 -0800 [thread overview]
Message-ID: <20100123230543.GG12679@spearce.org> (raw)
In-Reply-To: <1260231763-19194-3-git-send-email-jepler@unpythonic.net>
jepler@unpythonic.net wrote:
> From: Jeff Epler <jepler@unpythonic.net>
>
> Signed-off-by: Jeff Epler <jepler@unpythonic.net>
> ---
> git-gui.sh | 15 +++-
> lib/diff.tcl | 242 ++++++++++++++++++++++++++++++++++------------------------
> 2 files changed, 153 insertions(+), 104 deletions(-)
Thanks, applied.
--
Shawn.
prev parent reply other threads:[~2010-01-23 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 0:22 [PATCHv3 0/2] git-gui: (un)stage a range of changes at once jepler
2009-12-08 0:22 ` [PATCH 1/2] Fix applying a line when all following lines are deletions jepler
2009-12-08 0:22 ` [PATCH 2/2] Make it possible to apply a range of changes at once jepler
2010-01-23 23:05 ` Shawn O. Pearce [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=20100123230543.GG12679@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=jepler@unpythonic.net \
--cc=waste.manager@gmx.de \
/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).