From: "Shawn O. Pearce" <spearce@spearce.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Johannes Sixt <johannes.sixt@telecom.at>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-gui: Allow "Stage Line" to stage adjacent changes independently
Date: Wed, 16 Jul 2008 00:35:03 +0000 [thread overview]
Message-ID: <20080716003503.GA24339@spearce.org> (raw)
In-Reply-To: <7vy742zul7.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> 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.
...
> and try explaining what you are doing again, pretty please?
Me too. I really appreciate the effort spent to improve this
feature, but I really didn't follow the commit message at all. :-|
--
Shawn.
next prev parent reply other threads:[~2008-07-16 0:36 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 [this message]
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 ` [PATCH 2/2] git-gui: Allow "Stage Line" to stage adjacent changes independently Johannes Sixt
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=20080716003503.GA24339@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
/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.