From: Dave Abrahams <dave-xT6NqnoQrPdWk0Htik3J/w@public.gmane.org>
To: Git Mailing List <git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
magit <magit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Higher-level change review?
Date: Sun, 16 Oct 2011 10:31:51 -0400 [thread overview]
Message-ID: <m27h450zzc.fsf@pluto.luannocracy.com> (raw)
I've been working on a fairly large Org outline and also merging
upstream code changes in a project that does a lot of refactoring, and
I've discovered that Git's diff format is poorly-suited to reviewing the
kinds of structural modifications I often deal with, where indentation
changes and large parts of documents are reorganized. Are there better
ways to review, stage, etc. this kind of change than by using
straight-ahead diffs? And, for the magit list, has anyone integrated
an improved review capability with magit?
Hints most appreciated,
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next reply other threads:[~2011-10-16 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 14:31 Dave Abrahams [this message]
[not found] ` <m27h450zzc.fsf-NtBv8x4kbP9fRAUK6RR3EeqUGfbH9hYC@public.gmane.org>
2011-10-16 15:05 ` Higher-level change review? Tay Ray Chuan
[not found] ` <CALUzUxpr4FhjJ8OpYcpZOJLZuvveBNzKWd7soY6LQrz0Do1TDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-16 18:03 ` Jakub Narebski
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=m27h450zzc.fsf@pluto.luannocracy.com \
--to=dave-xt6nqnoqrpdwk0htik3j/w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.