git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Beau Martinez <beau@beaumartinez.com>
Cc: git@vger.kernel.org
Subject: Re: git add -p—splitting hunks, limit is too large
Date: Sun, 4 Sep 2016 10:01:36 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1609041000420.129229@virtualbox> (raw)
In-Reply-To: <CAEtDOuV+0CKRSu9mJa27+yQKJ-QRyNmwecrZKaaCh0St+VagZg@mail.gmail.com>

Hi Beau,

On Fri, 2 Sep 2016, Beau Martinez wrote:

> Hi git developers and community,
> 
> I'd like to inquire as to why `git add -p` can only split hunks so
> much. The limit is too large; why can't you split until each hunk is
> only a line? I often have to run `edit` and split them manually
> myself.

Please note that git gui lets you stage lines individually.

Ciao,
Johannes

      parent reply	other threads:[~2016-09-04  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 14:36 git add -p—splitting hunks, limit is too large Beau Martinez
2016-09-02 19:14 ` Jeff King
2016-09-02 19:49   ` Christian Neukirchen
2016-09-04  8:10   ` Johannes Schindelin
2016-09-04  8:01 ` Johannes Schindelin [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=alpine.DEB.2.20.1609041000420.129229@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=beau@beaumartinez.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 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).