git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ode <ode5002@blueyonder.co.uk>
To: git@vger.kernel.org
Subject: Staging Individual Lines
Date: Sun, 21 Apr 2013 23:22:49 +0100	[thread overview]
Message-ID: <517466B9.8010607@blueyonder.co.uk> (raw)

Hi,

I had a big commit I wanted to break up and was wondering if there is
any way to stage individual lines from the command line.

I am using git add -i but it couldn't split the hunks any smaller.

I went looking on Google and found git-cola gui client which works for
staging individual lines to the commit.

But it's a bit clumsy to do this with the mouse and I was wondering if
there is a way to do this without having manually editing the file and
changing the diff numbers in git add -i when it can't break the hunks
smaller.

Why must we still manually edit the diff numbers when git-cola seems to
be able to work out the changes automatically when adding single lines?

Thanks for your help.

             reply	other threads:[~2013-04-21 23:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 22:22 ode [this message]
2013-04-21 23:52 ` Staging Individual Lines Felipe Contreras
2013-04-22 14:35 ` Joshua Jensen

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=517466B9.8010607@blueyonder.co.uk \
    --to=ode5002@blueyonder.co.uk \
    --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).