From: Junio C Hamano <gitster@pobox.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [wishlist] git-add(1), git-restore(1): -U for more context (with -p)
Date: Sun, 13 Aug 2023 12:44:17 -0700 [thread overview]
Message-ID: <xmqq350mohgu.fsf@gitster.g> (raw)
In-Reply-To: <8bbfa6fe-fdaa-aeaf-51bc-16b3d3f7afaa@kernel.org> (Alejandro Colomar's message of "Sun, 13 Aug 2023 21:21:20 +0200")
Alejandro Colomar <alx@kernel.org> writes:
> It would be useful to have -U in git-add(1) and git-restore(1)
> to be able to see more context in combination with -p.
Even more useful would be to add commands to enlarge/shrink the
context to the interactive prompt, wouldn't it? Not all hunks need
unformly large context and having to decide how many lines of
context to ask upfront and having to stick to the choice during the
whole interactive session would be a bad interactive experience.
next prev parent reply other threads:[~2023-08-13 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 19:21 [wishlist] git-add(1), git-restore(1): -U for more context (with -p) Alejandro Colomar
2023-08-13 19:44 ` Junio C Hamano [this message]
2023-08-13 19:45 ` Alejandro Colomar
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=xmqq350mohgu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alx@kernel.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).