From: Graeme Geldenhuys <graemeg.lists@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: staging specific lines out of a hunk for a commit
Date: Tue, 21 Sep 2010 13:44:27 +0200 [thread overview]
Message-ID: <AANLkTimH5T8uKppW5PPe501OCVVRuLBtWfeSbUxka9Ov@mail.gmail.com> (raw)
In-Reply-To: <vpqocbrjpts.fsf@bauges.imag.fr>
On 21 September 2010 13:31, Matthieu Moy wrote:
>
> Otherwise, "git add -p", 'e' for 'e'dit, and delete the parts you
> don't want.
Ha, I was wondering about that, but wasn't sure if it would be
accepted or cause problems. Thanks for the tip.
--
Regards,
- Graeme -
_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net:8080/fpgui/
next prev parent reply other threads:[~2010-09-21 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:40 staging specific lines out of a hunk for a commit Graeme Geldenhuys
2010-09-21 10:52 ` Bert Wesarg
2010-09-21 11:00 ` Graeme Geldenhuys
2010-09-21 11:31 ` Matthieu Moy
2010-09-21 11:44 ` Graeme Geldenhuys [this message]
2010-09-21 11:09 ` Jonathan del Strother
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=AANLkTimH5T8uKppW5PPe501OCVVRuLBtWfeSbUxka9Ov@mail.gmail.com \
--to=graemeg.lists@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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).