git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <bebarino@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Stephan Beyer <s-beyer@gmx.net>,
	Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [RFC/PATCH 1/6] revert: libify cherry-pick and revert functionnality
Date: Wed, 03 Feb 2010 08:40:40 -0800	[thread overview]
Message-ID: <4B69A708.9030300@gmail.com> (raw)
In-Reply-To: <20100201075542.3929.38404.chriscool@tuxfamily.org>

On 01/31/2010 11:55 PM, Christian Couder wrote:
> +	if (flags&  PICK_REVERSE) {
> +		char *oneline_body = strchr(oneline, ' ');
> +
> +		base = commit;
> +		next = parent;
> +		strbuf_addstr(msg, "Revert \"");
> +		strbuf_addstr(msg, oneline_body + 1);
>    

Why not do the oneline_body + 1 during the strchr()? Seems like 
oneline_body is pointing to before the actual string we want.

> +		for (i = 0; i<  active_nr;) {
> +			struct cache_entry *ce = active_cache[i++];
> +			if (ce_stage(ce)) {
> +				strbuf_addstr(msg, "\t");
> +				strbuf_addstr(msg, ce->name);
> +				strbuf_addstr(msg, "\n");
>    

use strbuf_addch() for characters.

--->8----

diff --git a/pick.c b/pick.c
index bb04c68..1e1628a 100644
--- a/pick.c
+++ b/pick.c
@@ -145,12 +145,12 @@ int pick_commit(struct commit *pick_commit, int mainline,
         oneline = get_oneline(message);

         if (flags&  PICK_REVERSE) {
-               char *oneline_body = strchr(oneline, ' ');
+               char *oneline_body = strchr(oneline, ' ') + 1;

                 base = commit;
                 next = parent;
                 strbuf_addstr(msg, "Revert \"");
-               strbuf_addstr(msg, oneline_body + 1);
+               strbuf_addstr(msg, oneline_body);
                 strbuf_addstr(msg, "\"\n\nThis reverts commit ");
                 strbuf_addstr(msg, sha1_to_hex(commit->object.sha1));

@@ -196,9 +196,9 @@ int pick_commit(struct commit *pick_commit, int mainline, in
                 for (i = 0; i<  active_nr;) {
                         struct cache_entry *ce = active_cache[i++];
                         if (ce_stage(ce)) {
-                               strbuf_addstr(msg, "\t");
+                               strbuf_addch(msg, '\t');
                                 strbuf_addstr(msg, ce->name);
-                               strbuf_addstr(msg, "\n");
+                               strbuf_addch(msg, '\n');
                                 while (i<  active_nr&&  !strcmp(ce->name,
                                                 active_cache[i]->name))
                                         i++;

  parent reply	other threads:[~2010-02-03 16:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  7:55 [RFC/PATCH 0/6] add --ff option to cherry-pick Christian Couder
2010-02-01  7:55 ` [RFC/PATCH 1/6] revert: libify cherry-pick and revert functionnality Christian Couder
2010-02-01 10:26   ` Johannes Schindelin
2010-02-03 16:40   ` Stephen Boyd [this message]
2010-02-01  7:55 ` [RFC/PATCH 2/6] reset: refactor updating heads into a static function Christian Couder
2010-02-01  7:55 ` [RFC/PATCH 3/6] reset: refactor reseting in its own function Christian Couder
2010-02-01  7:55 ` [RFC/PATCH 4/6] reset: make reset function non static and declare it in "reset.h" Christian Couder
2010-02-01  7:55 ` [RFC/PATCH 5/6] revert: add --ff option to allow fast forward when cherry-picking Christian Couder
2010-02-01 11:10   ` Paolo Bonzini
2010-02-01 12:43     ` Christian Couder
2010-02-01 14:29       ` Paolo Bonzini
2010-02-02  5:13         ` Christian Couder
2010-02-02  7:56           ` Paolo Bonzini
2010-02-01  7:55 ` [RFC/PATCH 6/6] rebase -i: use new --ff cherry-pick option Christian Couder

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=4B69A708.9030300@gmail.com \
    --to=bebarino@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=s-beyer@gmx.net \
    --cc=torvalds@linux-foundation.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).