From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-gui: Allow "Stage Line" to stage adjacent changes independently
Date: Wed, 16 Jul 2008 09:15:15 +0200 [thread overview]
Message-ID: <487DA003.3090905@viscovery.net> (raw)
In-Reply-To: <7vy742zul7.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> Johannes Sixt <johannes.sixt@telecom.at> writes:
>
>> Consider this hunk:
>>
>> @@ -10,4 +10,4 @@
>> context before
>> -old 1
>> -old 2
>> +new 1
>> +new 2
>> context after
>>
>> [Nomenclature: to "stage change 2" means to stage lines "-old 1" and
>> "+new 1", in any order; likewise for "unstage" and "change 2".]
>
> You lost me.
>
> Do you mean to say that you always interpret the above hunk as:
>
> @@ -10,4 +10,4 @@
> context before
> -old 1
> +new 1
> -old 2
> +new 2
> context after
>
> and call "replace 'old 1' with 'new 1'" as "change 1", "replace 'old
> 2' with 'new 2'" as "change 2"?
No, it is not that I *always* interpret it this way. There is a problem to
fix only if I *want* to interpret it this way. Probably that's what I have
to make clear?
> If it is what you are doing, it does not make much sense to me. "new 1"
> may correspond to "old 1" and "old 2" while "new 2" may be an independent
> addition. E.g.
>
> @@ -10,4 +10,4 @@
> context before
> -#define add(x,y) \
> - (x) + (y)
> +#define add(x,y) ((x)+(y))
> +#define sub(x,y) ((x)-(y))
> context after
>
> I might want to pick bugfix of add() definition without using the new
> definition of sub().
In order to that, there is nothing to fix; you can do that today without
this patch.
> Please call
>
> "-old 1" - change #1
> "-old 2" - change #2
> "+new 1" - change #3
> "+new 2" - change #4
>
> and try explaining what you are doing again, pretty please?
No, this sounds like 4 independent changes, and that is not what this fix
is about.
I'll try to come up with a better wording.
-- Hannes
prev parent reply other threads:[~2008-07-16 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 21:11 [PATCH 1/2] git-gui: Fix "Stage/Unstage Line" with one line of context Johannes Sixt
2008-07-15 21:11 ` [PATCH 2/2] git-gui: Allow "Stage Line" to stage adjacent changes independently Johannes Sixt
2008-07-15 21:49 ` Junio C Hamano
2008-07-16 0:35 ` Shawn O. Pearce
2008-07-17 13:21 ` [PATCH 2/2 v2] git-gui: "Stage Line": Treat independent changes in adjacent lines better Johannes Sixt
2008-07-18 6:21 ` Junio C Hamano
2008-07-16 7:15 ` Johannes Sixt [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=487DA003.3090905@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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.