From: Eric Wong <normalperson@yhbt.net>
To: Adam Roben <aroben@apple.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Johannes Sixt <j.sixt@viscovery.net>,
Brian Downing <bdowning@lavos.net>
Subject: Re: Speed up git-svn fetch
Date: Fri, 25 Apr 2008 00:15:40 -0700 [thread overview]
Message-ID: <20080425071540.GA3589@untitled> (raw)
In-Reply-To: <480F8BB5.2040605@apple.com>
Adam Roben <aroben@apple.com> wrote:
> Adam Roben wrote:
> >I first sent this patch series 6 months ago today [1], then resent it after
> >some comments from Junio, Johannes, and Brian [2].
>
> Here are those links:
>
> [1] http://thread.gmane.org/gmane.comp.version-control.git/62098/focus=62102
> [2] http://thread.gmane.org/gmane.comp.version-control.git/62295/focus=62298
Thanks for following up on this, the Perl bits look good to me[1].
I commented in a separate email about the shell incompatibilities
I experienced.
I still the following gcc warnings when building it:
> hash-object.c: In function 'hash_stdin_paths':
> hash-object.c:43: warning: implicit declaration of function 'unquote_c_style'
Trivial fix:
--- a/hash-object.c
+++ b/hash-object.c
@@ -6,6 +6,7 @@
*/
#include "cache.h"
#include "blob.h"
+#include "quote.h"
> hash-object.c:51: warning: control reaches end of non-void function
This can probably just be a void.
> builtin-cat-file.c: In function 'cmd_cat_file':
> builtin-cat-file.c:224: warning: suggest parentheses around && within ||
Ugh, you added long (>80 char) lines to this and I'm having trouble
following it. I believe the git (like Linux) coding style calls for 80
char lines unless there is really no other way[2]. This is also a
problem for me in some of the shell tests, too.
> builtin-cat-file.c:151: warning: 'contents' may be used uninitialized in this function
gcc isn't smart here.
[1] - disclaimer, I'm not in my best mental state at this point in the
night/morning so maybe some things have slipped :)
[2] - Looking at your email address, I notice you work for a company that
pushes widescreen monitors, but I remain firmly on the side of dead tree
publishers whom I believe got line-wrapping right centuries ago :)
--
Eric Wong
prev parent reply other threads:[~2008-04-25 7:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 19:17 Speed up git-svn fetch Adam Roben
2008-04-23 19:17 ` [PATCH 01/11] Add tests for git cat-file Adam Roben
2008-04-23 19:17 ` [PATCH 02/11] git-cat-file: Small refactor of cmd_cat_file Adam Roben
2008-04-23 19:17 ` [PATCH 03/11] git-cat-file: Make option parsing a little more flexible Adam Roben
2008-04-23 19:17 ` [PATCH 04/11] git-cat-file: Add --batch-check option Adam Roben
2008-04-23 19:17 ` [PATCH 05/11] git-cat-file: Add --batch option Adam Roben
2008-04-23 19:17 ` [PATCH 06/11] Move git-hash-object tests from t5303 to t1007 Adam Roben
2008-04-23 19:17 ` [PATCH 07/11] Add more tests for git hash-object Adam Roben
2008-04-23 19:17 ` [PATCH 08/11] git-hash-object: Add --stdin-paths option Adam Roben
2008-04-23 19:17 ` [PATCH 09/11] Git.pm: Add command_bidi_pipe and command_close_bidi_pipe Adam Roben
2008-04-23 19:17 ` [PATCH 10/11] Git.pm: Add hash_and_insert_object and cat_blob Adam Roben
2008-04-23 19:17 ` [PATCH 11/11] git-svn: Speed up fetch Adam Roben
2008-04-25 18:04 ` [PATCH 03/11] git-cat-file: Make option parsing a little more flexible Junio C Hamano
2008-04-25 6:56 ` [PATCH 01/11] Add tests for git cat-file Eric Wong
2008-04-25 18:06 ` Junio C Hamano
2008-04-25 18:03 ` Junio C Hamano
2008-05-06 6:41 ` Junio C Hamano
2008-04-23 19:19 ` Speed up git-svn fetch Adam Roben
2008-04-25 7:15 ` Eric Wong [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=20080425071540.GA3589@untitled \
--to=normalperson@yhbt.net \
--cc=aroben@apple.com \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.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).