From: Derrick Stolee <stolee@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 9/9] commit-reach.h: add missing declarations (hdr-check)
Date: Wed, 19 Sep 2018 19:38:57 -0400 [thread overview]
Message-ID: <eb77d563-8b3e-9b00-59b8-b050e6378c69@gmail.com> (raw)
In-Reply-To: <089b2111-b7e9-6795-b04a-ed259f78796a@ramsayjones.plus.com>
On 9/18/2018 8:15 PM, Ramsay Jones wrote:
> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
> commit-reach.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/commit-reach.h b/commit-reach.h
> index 7d313e2975..f41d8f6ba3 100644
> --- a/commit-reach.h
> +++ b/commit-reach.h
> @@ -1,12 +1,13 @@
> #ifndef __COMMIT_REACH_H__
> #define __COMMIT_REACH_H__
>
> +#include "commit.h"
> #include "commit-slab.h"
>
> -struct commit;
> struct commit_list;
> -struct contains_cache;
Interesting that you needed all of commit.h here, and these 'struct
commit' and 'struct contains_cache' were not enough. Was there a reason
you needed the entire header file instead of just adding a missing
struct declaration?
> struct ref_filter;
> +struct object_id;
> +struct object_array;
>
> struct commit_list *get_merge_bases_many(struct commit *one,
> int n,
These look like standard inclusions. Thanks!
next prev parent reply other threads:[~2018-09-20 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 0:15 [PATCH 9/9] commit-reach.h: add missing declarations (hdr-check) Ramsay Jones
2018-09-19 23:38 ` Derrick Stolee [this message]
2018-09-20 15:35 ` Ramsay Jones
2018-09-21 17:41 ` Derrick Stolee
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=eb77d563-8b3e-9b00-59b8-b050e6378c69@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsayjones.plus.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).