From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Montalbo <mmontalbo@gmail.com>,
git@vger.kernel.org, Patrick Steinhardt <pks@pks.im>
Subject: Re: [RFC PATCH 07/14] odb: gather the odb sources under odb/
Date: Mon, 24 Aug 2026 22:03:50 +0200 [thread overview]
Message-ID: <aoyjpmBXUhj_PPck@ugly.lan> (raw)
In-Reply-To: <xmqqjypfshnh.fsf@gitster.g>
On Mon, Aug 24, 2026 at 07:43:46AM -0700, Junio C Hamano wrote:
>Oswald Buddenhagen <oswald.buddenhagen@gmx.de> writes:
>> On Sun, Aug 23, 2026 at 10:18:51AM -0700, Michael Montalbo wrote:
>>>Move the 23 odb C sources and 26 headers into odb/ as renames.
>>>
>> i for one would go with lib/odb/.
>>
>I do not agree with lib/odb/ suggestion,
>
why not? it's hugely beneficial for the comprehensibility of the build
system and discoverability when the physical project structure follows
the logical one.
>>>+++ b/builtin/add.c
>>>-#include "object-file.h"
>>>-#include "odb.h"
>>>+#include "odb/object-file.h"
>>>+#include "odb/odb.h"
>>>
>> that's the wrong include style here.
>> it was already wrong in a lot of places, but as you rewrite everything
>> anyway, you could fix it just as well.
>
>Do you mean they should not be quoted in a pair of double quotes
>because the behaviour of such includes is implementation-defined
>(instead use "<>" as we use -I<path> on the command line)?
>
yes.
(actually, i don't mind relying on the popular interpretation that
""-style means relative to the including file's containing directory.
that mostly implies that "" is ok for in-module references when headers
and sources live side by side.)
> Something else?
>
everything else i can think of would require more context, so it's a
good first guess to assume that i didn't mean it.
next prev parent reply other threads:[~2026-08-24 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 17:18 [RFC PATCH 00/14] git organize: record file placement and apply it Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 01/14] organize: add the git organize builtin Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 02/14] organize: add the labeler, organizer, and apply --labels-only Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 03/14] organize: add status --exit-code Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 04/14] organize: add the --label selector Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 05/14] organize: declare Git's scope and layout Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 06/14] organize: record a label for every source in scope Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 07/14] odb: gather the odb sources under odb/ Michael Montalbo
2026-08-24 14:08 ` Oswald Buddenhagen
2026-08-24 14:43 ` Junio C Hamano
2026-08-24 20:03 ` Oswald Buddenhagen [this message]
2026-08-23 17:18 ` [RFC PATCH 08/14] refs: gather the refs sources under refs/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 09/14] pack: gather the pack sources under pack/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 10/14] diff: gather the diff sources under diff/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 11/14] revision: gather the revision sources under revision/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 12/14] index: gather the index sources under index/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 13/14] setup: gather the setup sources under setup/ Michael Montalbo
2026-08-23 17:18 ` [RFC PATCH 14/14] transport: gather the transport sources under transport/ Michael Montalbo
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=aoyjpmBXUhj_PPck@ugly.lan \
--to=oswald.buddenhagen@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mmontalbo@gmail.com \
--cc=pks@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.