[dropping cc's because I think most people don't care about this bit]
On Thu, Aug 28, 2008 at 04:22:12PM -0700, Perry Wagle wrote:
I saw some talk of efficiency, but it was mainly "100,000 files in one
directory makes your filesystem performance suck". But maybe somebody
talked about the shell. I think there is "143 is too many, and scares
new users". And I think there is "systems with hardlink problems ended
up with 100+ copies of the git binary, which is big". For the latter,
you could still keep git-* with a much smaller wrapper, of course.
I think there is a recognition that some of the commands aren't really
that useful to end users, but are kept around as helpers or as scripts.
For example, the interactive mode of "git add" is implemented in perl
(while the rest is implemented in C). So it is purely an implementation
issue that the script git-add--interactive exists. Nobody should be
calling it directly, but rather going through "git add -i", which will
call it as necessary with the right command line options.
Good. :)
-Peff
--
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