From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] refactor dir_add_name
Date: Tue, 12 Jun 2007 23:51:04 +0200 [thread overview]
Message-ID: <20070612215104.GB21858@diku.dk> (raw)
In-Reply-To: <7v7iq9lk76.fsf@assigned-by-dhcp.pobox.com>
Junio C Hamano <gitster@pobox.com> wrote Tue, Jun 12, 2007:
> Anyway, it appears that Jonas picked up your patch to polish up,
> so I won't touch this series until that resurfaces.
My idea was to put the nr, alloc, and entries members into a separate
struct dir_entry_list, which should allow the dir_add_* functions to be
"united" and thus somewhat remove the need for alloc_grow. However,
after spending some time on it, changing dir.nr to dir.entry_list.nr
etc. reduced readability so much that I ended up trying to make other
cleanups and the simplicity of the series was lost.
Anyway, I don't think I can come up with a more polished version without
adding a few cleanup patches along the way. So I think apart from the
amended version of 3/3 I will take back my intension to polish it up.
--
Jonas Fonseca
next prev parent reply other threads:[~2007-06-12 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 20:46 Adding empty directory gives bogus error message Jonas Fonseca
2007-06-11 12:30 ` Jeff King
2007-06-11 13:39 ` [PATCH 1/3] refactor dir_add_name Jeff King
2007-06-11 14:13 ` Johannes Schindelin
2007-06-11 16:23 ` Junio C Hamano
2007-06-11 19:46 ` Jeff King
2007-06-12 7:13 ` Junio C Hamano
2007-06-12 12:19 ` Jeff King
2007-06-12 21:51 ` Jonas Fonseca [this message]
2007-06-11 13:39 ` [PATCH 2/3] dir_struct: add collect_ignored option Jeff King
2007-06-11 13:39 ` [PATCH 3/3] builtin-add: simplify (and increase accuracy of) exclude handling Jeff King
2007-06-11 15:01 ` Jonas Fonseca
2007-06-11 15:54 ` Jeff King
2007-06-11 19:15 ` Jonas Fonseca
2007-06-11 19:48 ` Jeff King
2007-06-12 21:42 ` Jonas Fonseca
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=20070612215104.GB21858@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.