login
Header Space

 
 

Re: [PATCH 2/3] cached-sha1-map: refactoring hash traversal code

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Geoffrey Irving <irving@...>
Cc: Johannes Schindelin <Johannes.Schindelin@...>, git@vger.kernel.org <git@...>, Junio C Hamano <gitster@...>
Date: Wednesday, July 9, 2008 - 1:27 am

"Geoffrey Irving" <irving@naml.us> writes:


Sign-off?


The refactoring is good, and it should have been that way from the
beginning.  Please don't send in "introduce foo.c [1/N]", "oops, initial
version of foo.c was crap, here is a fixup [2/N]".


Does this have to be extern?

If you are designing an API from scratch, and if you want a long, use it
consistently.  Do not demote an int to shorter int in a callchain
unnecessarily.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 2/3] cached-sha1-map: refactoring hash traversal code, Geoffrey Irving, (Tue Jul 8, 11:56 pm)
Re: [PATCH 2/3] cached-sha1-map: refactoring hash traversal ..., Junio C Hamano, (Wed Jul 9, 1:27 am)
speck-geostationary