From: Jakub Narebski <jnareb@gmail.com>
To: William Pursell <bill.pursell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: summaries in git add --patch
Date: Thu, 27 Nov 2008 13:27:19 -0800 (PST) [thread overview]
Message-ID: <m3od00kgg9.fsf@localhost.localdomain> (raw)
In-Reply-To: <492F0CAD.3010101@gmail.com>
William Pursell <bill.pursell@gmail.com> writes:
> I just implemented a command to give a brief summary
> of the patches in the current file.
Good idea.
Side note: you should signoff your patches, following
Documentation/SubmittingPatches. And it would be better
if the patches itself were either threaded, or all be
replies to this cover letter ([PATCH 0/5]) email.
> Please note that
> I am just rediscovering perl after having abandoned it
> years ago, so any criticism is appreciated. 5 patches
> to follow. (From aa14a0c3f)
>
> Here's a screen shot:
>
>
> Stage this hunk [y,n,a,l,d,k,K,j,J,e,?]? l
> '*' indicates current hunk. '+' stage, '-' don't stage
> 0+: @@ -8,9 +8,9 @@ Aani
> 1 : @@ -48,7 +48,7 @@ abandonable
> *2 : @@ -88,7 +88,7 @@ abaton
I hope that contrary to this 'screenshot' actual output is aligned
properly...
> 3 : @@ -128,7 +128,7 @@ abdest
> 4-: @@ -81192,9 +81192,9 @@ gyrous
> 5 : @@ -234925,7 +234925,7 @@ zymotic
That of course assumes that summary catches right thing; still
it is better than nothing.
> @@ -88,7 +88,7 @@ abaton
> abator
> abattoir
> Abatua
> -abature
> +agature
> abave
> abaxial
> abaxile
Same here.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-11-27 21:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 21:10 summaries in git add --patch William Pursell
2008-11-27 21:27 ` Jakub Narebski [this message]
2008-11-28 0:34 ` Junio C Hamano
2008-11-28 4:36 ` William Pursell
2008-11-28 6:42 ` William Pursell
2008-11-28 7:24 ` Junio C Hamano
2008-11-29 0:22 ` William Pursell
2008-12-03 2:15 ` Junio C Hamano
2008-12-03 20:38 ` summaries in git add --patch[PATCH 1/2] William Pursell
2008-12-03 23:22 ` Junio C Hamano
2008-12-04 6:55 ` William Pursell
2008-12-04 8:47 ` Junio C Hamano
2008-12-04 10:43 ` William Pursell
2008-12-05 2:23 ` Junio C Hamano
2008-12-03 20:39 ` summaries in git add --patch[PATCH 2/2] William Pursell
2008-12-03 23:23 ` Junio C Hamano
2008-12-04 6:56 ` William Pursell
2008-12-04 9:00 ` Junio C Hamano
2008-12-04 10:43 ` William Pursell
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=m3od00kgg9.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bill.pursell@gmail.com \
--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 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.