From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: git@vger.kernel.org
Subject: [Feature request] git add -i should have option for showing more context
Date: Tue, 05 Aug 2014 20:29:58 +0200 [thread overview]
Message-ID: <53E122A6.8040608@o2.pl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
In git add -i when staging the modifications piecemail by patching there
should be a command for showing more context.
It can be sometimes difficult to determine whether any hunk should be staged
without refering to more source code.
As a command I mean a choice in the following list:
Stage this hunk [y,n,q,a,d,/,e,?]? ?
y - stage this hunk
n - do not stage this hunk
q - quit; do not stage this hunk nor any of the remaining ones
a - stage this hunk and all later hunks in the file
d - do not stage this hunk nor any of the later hunks in the file
g - select a hunk to go to
/ - search for a hunk matching the given regex
j - leave this hunk undecided, see next undecided hunk
J - leave this hunk undecided, see next hunk
k - leave this hunk undecided, see previous undecided hunk
K - leave this hunk undecided, see previous hunk
s - split the current hunk into smaller hunks
e - manually edit the current hunk
? - print help
- --
Pozdrawiam,
Mateusz Jończyk
AEI, Informatyka, Semestr 3 Magisterskich, BDiIS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: My public key: 0x2C64C488 on hkp://pool.sks-keyservers.net
iQEcBAEBAgAGBQJT4SKmAAoJELLT9LcsZMSI+WMH/1DoOuBFsDLjDF9zMFmeGbGf
bYDEgpMgCWVHT+v9YMoY41ZMLOABni+7E4yvym/x5mO00Q4LPsXfDTNeHC7LEcgJ
uDLS9Lx3A3eXoqZFsIsXKY6+SHr8RU8UJRdppVakMq2novitzJrAjt3HZUO5ai8n
bmWIF3HBNZcKHfVQSGuBCNB1ZWxlKv7gRPl/RFeCv+Z9kiYKUO/TXMEya3mxXFd3
3u7XEJw5G4KyN7ySVH6kRKcCIp6L0cRhKtyuFILs7EMO5e59HYr2JKpParnc0CXd
gU1rVCwYW2GL6cDekabWoffxuKSCTg74IeI5Gu0oTyYeK3N93yPJudGgTLMqHGM=
=Kl4N
-----END PGP SIGNATURE-----
reply other threads:[~2014-08-05 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53E122A6.8040608@o2.pl \
--to=mat.jonczyk@o2.pl \
--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.