From: Clemens Buchacher <drizzd@aon.at>
To: Markus Heidelberg <markus.heidelberg@web.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] Revert "git gui: show diffs with a minimum of 1 context line"
Date: Sun, 24 May 2009 01:16:06 +0200 [thread overview]
Message-ID: <20090523231605.GA4522@localhost> (raw)
In-Reply-To: <1243099727-5272-1-git-send-email-markus.heidelberg@web.de>
On Sat, May 23, 2009 at 07:28:47PM +0200, Markus Heidelberg wrote:
> Diffs without context can actually be useful. Depending on the changes
> it can be less distracting to read them or to get an overview.
Maybe so. But as stated in the commit message of 55ba8a3 (git gui: show
diffs with a minimum of 1 context line) context-less diff was disabled
because it caused bugs with staging. However, I never got around to fix the
real cause of the problem. See the original thread at
http://article.gmane.org/gmane.comp.version-control.git/94387
next prev parent reply other threads:[~2009-05-23 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 17:28 [PATCH] Revert "git gui: show diffs with a minimum of 1 context line" Markus Heidelberg
2009-05-23 23:16 ` Clemens Buchacher [this message]
2009-05-24 10:01 ` Markus Heidelberg
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=20090523231605.GA4522@localhost \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--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).