From: Timo Hirvonen <tihirvon@gmail.com>
To: fork0@t-online.de
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de, junkio@cox.net
Subject: Re: [PATCH 1/4] merge-recursive in C
Date: Mon, 3 Jul 2006 18:46:04 +0300 [thread overview]
Message-ID: <20060703184604.59801e4e.tihirvon@gmail.com> (raw)
In-Reply-To: <20060630002721.GA22618@steel.home>
fork0@t-online.de (Alex Riesen) wrote:
> +/* in place */
> +void path_list_union_update(struct path_list *dst, const struct path_list *src)
> +{
> + char **new_paths;
> + int i = 0, j = 0, nr = 0, alloc = dst->nr + dst->nr;
It should be alloc = dst->nr + src->nr.
--
http://onion.dynserv.net/~timo/
next prev parent reply other threads:[~2006-07-03 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 0:27 [PATCH 1/4] merge-recursive in C Alex Riesen
2006-07-03 15:46 ` Timo Hirvonen [this message]
2006-07-03 15:54 ` Johannes Schindelin
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=20060703184604.59801e4e.tihirvon@gmail.com \
--to=tihirvon@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=fork0@t-online.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).