From: Pavel Roskin <proski@gnu.org>
To: Ryan Anderson <ryan@michonline.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Move all builtin .c files into builtin/
Date: Mon, 10 Jul 2006 02:41:19 -0400 [thread overview]
Message-ID: <1152513679.3504.47.camel@dv> (raw)
In-Reply-To: <11525072491512-git-send-email-ryan@michonline.com>
Hello, Ryan!
On Mon, 2006-07-10 at 00:54 -0400, Ryan Anderson wrote:
> Signed-off-by: Ryan Anderson <ryan@michonline.com>
I agree that the top level directory is overcrowded, but wouldn't it be
better to move libgit.a sources to "lib" and then classify the remaining
files in some way (e.g. "git" or "src" for builtin commands, "commands"
for the rest)? While at that, the "buildin-" prefix could be stripped.
The main "git" executable is nothing but several builtin commands rolled
together. It's not like a shell, which has functionality beyond the
builtin commands. So "builtin" is git.
Or you can say that the git executable is a command line frontend to the
git library (it's moving in this direction anyway). Then you can have
"client" and "server" directories. That's more important for
understanding the source than "builtin", "standalone" or any
classification based on technical details.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-07-10 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 4:54 [RFC+PATCH 0/2] Clean up root directory Ryan Anderson
2006-07-10 4:54 ` [PATCH 1/2] Move SCM interoperability tools into interop/ Ryan Anderson
2006-07-10 4:54 ` [PATCH 2/2] Move all builtin .c files into builtin/ Ryan Anderson
2006-07-10 6:41 ` Pavel Roskin [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=1152513679.3504.47.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.com \
/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).