From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Pavel Roskin <proski@gnu.org>, git@vger.kernel.org
Subject: Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards
Date: Mon, 8 Aug 2005 19:10:36 -0400 [thread overview]
Message-ID: <20050808231036.GA22778@mythryan2.michonline.com> (raw)
In-Reply-To: <7vy87c2lrv.fsf@assigned-by-dhcp.cox.net>
On Mon, Aug 08, 2005 at 01:53:24PM -0700, Junio C Hamano wrote:
> I do want to revisit Makefile issues after 0.99.4, along with
> the changes Pasky sent several days ago. Please remind me about
> them after Wednesday.
We should discuss (or just do) a reorganization of how we lay out the
source tree.
There's probably a few too many files in the top directory, from all the
porcelain we've built on the plumbing. (heh)
I haven't really given a lot of thought to this yet, but I was thinking
of something along these lines:
Rename tools/ to mail-tools/, push git-send-email-script into that.
Create a "porcelain" directory for things like git-bisect-script
Create a "core" directory for things like "git-commit-script"
Create a "src" (?) directory for *.[ch]
Maybe move documentation into the same directory as the scripts they
belong to.
Then we can argue over where the leftover things fall.
If we can get the directory structure to make sense and start putting
new things into the right spots, the exact location of where *current*
things end up is probably not so important.
I consider this post 1.0 material, personally.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-08-08 23:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 5:36 [PATCH] Making CFLAGS compilant with GNU Coding Standards Pavel Roskin
2005-08-08 20:53 ` Junio C Hamano
2005-08-08 23:10 ` Ryan Anderson [this message]
2005-08-08 23:42 ` Johannes Schindelin
2005-08-09 2:48 ` Junio C Hamano
2005-08-09 10:17 ` Sanity check of git-commit patch, was " Johannes Schindelin
2005-08-09 12:53 ` Junio C Hamano
2005-08-09 14:19 ` Johannes Schindelin
2005-08-09 17:00 ` Junio C Hamano
2005-08-10 2:20 ` Horst von Brand
2005-08-10 12:52 ` Johannes Schindelin
2005-08-10 5:45 ` Junio C Hamano
2005-08-09 12:56 ` Junio C Hamano
2005-08-11 4:01 ` Pavel Roskin
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=20050808231036.GA22778@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.org \
/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).