From: Ping Yin <pkufranky@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: A question about using 'add -p' to split the patch
Date: Mon, 15 Jun 2009 16:56:40 +0800 [thread overview]
Message-ID: <46dff0320906150156mf9ac4dek99c94a6cc59e1db@mail.gmail.com> (raw)
In-Reply-To: <20090615073635.GA53643@gmail.com>
>
> For add -e I got it to work by editing the patch to;
>
> +function bt_move($path, $pos) {
> + return;
> +}
> function bt_add($path) {
> return;
> }
>
> The reason it's hard to get right is that you have to
> reconstruct the context of the original content for the
> adds/removes and remember to add the space before the
> reconstructed bt_add($path).
>
Thanks very much, i forgot the space before the reconstructed bt_add($path) :-)
prev parent reply other threads:[~2009-06-15 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 3:08 A question about using 'add -p' to split the patch Ping Yin
2009-06-15 6:12 ` David Aguilar
2009-06-15 6:24 ` Ping Yin
2009-06-15 7:36 ` David Aguilar
2009-06-15 8:56 ` Ping Yin [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=46dff0320906150156mf9ac4dek99c94a6cc59e1db@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=davvid@gmail.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).