From: "Shawn O. Pearce" <spearce@spearce.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] Move bundle specific stuff into bundle.[ch]
Date: Tue, 17 Jul 2007 23:29:07 -0400 [thread overview]
Message-ID: <20070718032907.GY32566@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707172302560.14596@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> wrote:
> (Someday, I'd like to have a diff that can show that a substantial block
> of '+' lines matches a block of lines from somewhere in the "before"
> content, so reviewers can verify that the patch reorders code but doesn't
> change it, or changes it in certain ways. But, of course, that's both hard
> to generate and hard to display usefully.)
I just moved a huge block in git-gui so I have a great example...
What about a patch format like this? I doubt people move more than
26 blocks in the same patch of the same file, so using a single
character block prefix when the before/after images are identical
might work OK.
diff --git a/git-gui.sh b/git-gui.sh
index 0443129..f13fa80 100755
--- a/git-gui.sh
+++ b/git-gui.sh
a@@ -632,6 +632,43 a@@ You are using [git-version]:
######################################################################
##
a+## feature option selection
a+
a+if {[regexp {^git-(.+)$} [appname] _junk subcommand]} {
a+ unset _junk
a+} else {
a+ set subcommand gui
a+}
a+if {$subcommand eq {gui.sh}} {
a+ set subcommand gui
a+}
a+if {$subcommand eq {gui} && [llength $argv] > 0} {
a+ set subcommand [lindex $argv 0]
a+ set argv [lrange $argv 1 end]
a+}
a+
a+enable_option multicommit
a+enable_option branch
a+enable_option transport
a+
a+switch -- $subcommand {
a+browser -
a+blame {
a+ disable_option multicommit
a+ disable_option branch
a+ disable_option transport
a+}
a+citool {
a+ enable_option singlecommit
a+
a+ disable_option multicommit
a+ disable_option branch
a+ disable_option transport
a+}
a+}
a+
a+######################################################################
a+##
## repository setup
if {[catch {
a@@ -1598,43 +1635,6 a@@ apply_config
######################################################################
##
a-## feature option selection
a-
a-if {[regexp {^git-(.+)$} [appname] _junk subcommand]} {
a- unset _junk
a-} else {
a- set subcommand gui
a-}
a-if {$subcommand eq {gui.sh}} {
a- set subcommand gui
a-}
a-if {$subcommand eq {gui} && [llength $argv] > 0} {
a- set subcommand [lindex $argv 0]
a- set argv [lrange $argv 1 end]
a-}
a-
a-enable_option multicommit
a-enable_option branch
a-enable_option transport
a-
a-switch -- $subcommand {
a-browser -
a-blame {
a- disable_option multicommit
a- disable_option branch
a- disable_option transport
a-}
a-citool {
a- enable_option singlecommit
a-
a- disable_option multicommit
a- disable_option branch
a- disable_option transport
a-}
a-}
a-
a-######################################################################
a-##
## ui construction
set ui_comm {}
--
1.5.3.rc1.818.g84b7
--
Shawn.
next prev parent reply other threads:[~2007-07-18 3:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 22:49 [PATCH 1/3] Move bundle specific stuff into bundle.[ch] Johannes Schindelin
2007-07-18 2:48 ` Daniel Barkalow
2007-07-18 3:23 ` Daniel Barkalow
2007-07-18 3:29 ` Shawn O. Pearce [this message]
2007-07-18 6:13 ` Junio C Hamano
2007-07-18 6:19 ` Shawn O. Pearce
2007-07-18 7:26 ` Junio C Hamano
2007-07-18 10:09 ` Johannes Schindelin
2007-07-18 9:56 ` Johannes Schindelin
2007-07-18 16:25 ` Daniel Barkalow
2007-07-18 16:33 ` Johannes Schindelin
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=20070718032907.GY32566@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--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).