git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heba Waly <heba.waly@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Heba Waly via GitGitGadget <gitgitgadget@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/1] [Outreachy] doc: remove api-index
Date: Sun, 10 Nov 2019 14:06:39 +1300	[thread overview]
Message-ID: <CACg5j25S8eJN5Sc9cm_DEu50bmaR5fQBT7dAid2z-Be2y_rpmg@mail.gmail.com> (raw)
In-Reply-To: <xmqq7e4cqk9y.fsf@gitster-ct.c.googlers.com>

On Thu, Nov 7, 2019 at 7:21 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> "Heba Waly via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > Remove both api-index.txt and api-index-skel.txt as the API documentation is
> > being moved to the header files, so the index is not needed anymore because
> > the doc files (Documentation/technical/api-*.txt) will be gone.
> >
> > Make changes to Documentation/Makefile accordingly.
>
> Why is this not part of the other series?  Without any of them this
> step does not make sense, no?

Moving it to the other series makes more sense, although I won't
consider it dependent on removing the rest of the files, as we're
changing the location of the documentation anyway, and readers will
need to refer to the code for more info. But I agree with you and will
move it there.

Thanks,
Heba

      reply	other threads:[~2019-11-10  1:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 12:48 [PATCH 0/1] [Outreachy] doc: remove api-index Heba Waly via GitGitGadget
2019-11-06 12:48 ` [PATCH 1/1] api-index: remove api doc index files Heba Waly via GitGitGadget
2019-11-07  6:21 ` [PATCH 0/1] [Outreachy] doc: remove api-index Junio C Hamano
2019-11-10  1:06   ` Heba Waly [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=CACg5j25S8eJN5Sc9cm_DEu50bmaR5fQBT7dAid2z-Be2y_rpmg@mail.gmail.com \
    --to=heba.waly@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.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).