git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
	git@vger.kernel.org, Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: [PATCH 4/4] builtin: use builtin.h for all builtin commands
Date: Sun, 14 Nov 2010 10:55:37 -0800	[thread overview]
Message-ID: <7v8w0v3fbq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTi=SbqD_3yYsRGCsmSxh-B8kpupnjq0XPGjMsxdK@mail.gmail.com> (Sverre Rabbelier's message of "Sun\, 14 Nov 2010 16\:01\:10 +0100")

Sverre Rabbelier <srabbelier@gmail.com> writes:

> On Sun, Nov 14, 2010 at 15:44, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>> diff --git a/wt-status.c b/wt-status.c
>> index fc2438f..bfc97fb 100644
>> --- a/wt-status.c
>> +++ b/wt-status.c
>> @@ -1,4 +1,4 @@
>> -#include "cache.h"
>> +#include "builtin.h"
>
> Doesn't this suggest wt-status.c should be moved to builtin? Or
> something like that.

Why?  builtin.h is to declare cmd_foo() and to be included by files that
implement cmd_foo() (i.e. builtin/*.c) and the file that needs to see
cmd_foo() declarations (i.e. git.c).

wt-status.c is about giving common service routines for status related
commands in builtin/commit.c to implement both commit and status.  Its
services may have gained callers outside builtin/cocmmit.c, but that is
not a good reason to export its services via builtin.h nor for it to
include builtin.h.

This is a tangent but I think for the same reason the types and functions
related to notes-rewrite currently in builtin.h do not belong there; they
should be moved to notes.h or somewhere.

  parent reply	other threads:[~2010-11-14 18:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 14:44 [PATCH 0/4] [PULL] ab/i18n-prereqs, prerequisites for ab/i18n Ævar Arnfjörð Bjarmason
2010-11-14 14:44 ` [PATCH 1/4] Makefile: move "Platform specific tweaks" above LIB_{H,OBJS} Ævar Arnfjörð Bjarmason
2010-11-14 17:23   ` Jonathan Nieder
2010-11-14 17:51     ` Ævar Arnfjörð Bjarmason
2010-11-14 18:51       ` Jonathan Nieder
2010-11-15 16:07         ` Junio C Hamano
2010-11-15 16:11           ` Jonathan Nieder
2010-11-15 16:16             ` Ævar Arnfjörð Bjarmason
2010-11-14 19:12       ` Junio C Hamano
2010-11-14 17:53     ` Jonathan Nieder
2010-11-14 19:08   ` Junio C Hamano
2010-11-14 14:44 ` [PATCH 2/4] t7004-tag.sh: re-arrange git tag comment for clarity Ævar Arnfjörð Bjarmason
2010-11-14 17:32   ` Jonathan Nieder
2010-11-14 17:57     ` Ævar Arnfjörð Bjarmason
2010-11-14 14:44 ` [PATCH 3/4] tests: use test_cmp instead of piping to diff(1) Ævar Arnfjörð Bjarmason
2010-11-14 17:41   ` Jonathan Nieder
2010-11-14 14:44 ` [PATCH 4/4] builtin: use builtin.h for all builtin commands Ævar Arnfjörð Bjarmason
2010-11-14 15:01   ` Sverre Rabbelier
2010-11-14 15:11     ` Ævar Arnfjörð Bjarmason
2010-11-14 18:55     ` Junio C Hamano [this message]
2010-11-14 17:47   ` Jonathan Nieder
2010-11-17 19:54   ` Junio C Hamano
2010-11-17 20:08     ` Ævar Arnfjörð Bjarmason
2010-11-17 20:15       ` Jonathan Nieder
2010-11-14 17:50 ` [PATCH 0/4] [PULL] ab/i18n-prereqs, prerequisites for ab/i18n Jonathan Nieder

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=7v8w0v3fbq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=srabbelier@gmail.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).