git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heba Waly via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Heba Waly <heba.waly@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/1] [Outreachy] documentation: remove empty doc files
Date: Wed, 23 Oct 2019 07:25:55 +0000	[thread overview]
Message-ID: <pull.412.v2.git.1571815556.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.412.git.1571768375.gitgitgadget@gmail.com>

Remove empty and redundant documentation files from the
Documentation/technical/ directory.

The empty doc files included only TODO messages with no documentation for
years. Instead an approach is being taken to keep all doc beside the code in
the relevant header files. Having empty doc files is confusing and
disappointing to anybody looking for information, besides having the
documentation in header files makes it easier for developers to find the
information they are looking for.

here's a list of the files removed and if the info can be found in the
corresponding header file: 1- Documentation/technical/api-grep.txt -> grep.h
does not have enough documentation at the moment. 2-
Documentation/technical/api-object-access.txt -> sha1-file.c and object.h
have some details 3- Documentation/technical/api-quote.txt -> quote.h has
some details. 4- Documentation/technical/api-xdiff-interface.txt ->
xdiff-interface.h has some details.

Signed-off-by: Heba Waly heba.waly@gmail.com [heba.waly@gmail.com]

Heba Waly (1):
  documentation: remove empty doc files

 Documentation/technical/api-grep.txt            |  8 --------
 Documentation/technical/api-object-access.txt   | 15 ---------------
 Documentation/technical/api-quote.txt           | 10 ----------
 Documentation/technical/api-xdiff-interface.txt |  7 -------
 4 files changed, 40 deletions(-)
 delete mode 100644 Documentation/technical/api-grep.txt
 delete mode 100644 Documentation/technical/api-object-access.txt
 delete mode 100644 Documentation/technical/api-quote.txt
 delete mode 100644 Documentation/technical/api-xdiff-interface.txt


base-commit: d966095db01190a2196e31195ea6fa0c722aa732
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-412%2FHebaWaly%2Fdelete_empty_docs-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-412/HebaWaly/delete_empty_docs-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/412

Range-diff vs v1:

 1:  ffdde613d8 ! 1:  5cd79e24fe documentation: remove empty doc files
     @@ -5,13 +5,22 @@
          Remove empty and redundant documentation files from the
          Documentation/technical/ directory.
      
     -    As part of moving the documentation from Documentation/technical/api-* to
     -    header files, the following files are deleted because they include only
     -    TODO messages with no documentation to be moved:
     -    Documentation/technical/api-grep.txt
     -    Documentation/technical/api-object-access.txt
     -    Documentation/technical/api-quote.txt
     -    Documentation/technical/api-xdiff-interface.txt
     +    The empty doc files included only TODO messages with no documentation for
     +    years. Instead an approach is being taken to keep all doc beside the code
     +    in the relevant header files.
     +    Having empty doc files is confusing and disappointing to anybody looking
     +    for information, besides having the documentation in header files makes it
     +    easier for developers to find the information they are looking for.
     +
     +    here's a list of the files removed and if the info can be found in the
     +    corresponding header file:
     +    1- Documentation/technical/api-grep.txt -> grep.h does not have enough
     +    documentation at the moment.
     +    2- Documentation/technical/api-object-access.txt -> sha1-file.c and
     +    object.h have some details
     +    3- Documentation/technical/api-quote.txt -> quote.h has some details.
     +    4- Documentation/technical/api-xdiff-interface.txt -> xdiff-interface.h has
     +    some details.
      
          Signed-off-by: Heba Waly <heba.waly@gmail.com>
      

-- 
gitgitgadget

  parent reply	other threads:[~2019-10-23  7:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 18:19 [PATCH 0/1] [Outreachy] documentation: remove empty doc files Heba Waly via GitGitGadget
2019-10-22 18:19 ` [PATCH 1/1] " Heba Waly via GitGitGadget
2019-10-22 21:04   ` Emily Shaffer
2019-10-22 23:51     ` Junio C Hamano
2019-10-23  7:23       ` Heba Waly
2019-10-23  7:22     ` Heba Waly
2019-10-23  7:25 ` Heba Waly via GitGitGadget [this message]
2019-10-23  7:25   ` [PATCH v2 " Heba Waly via GitGitGadget
2019-10-23 21:44     ` Emily Shaffer
2019-10-24 10:43       ` Heba Waly
2019-10-24 11:29   ` [PATCH v3 0/1] [Outreachy] " Heba Waly via GitGitGadget
2019-10-24 11:29     ` [PATCH v3 1/1] " Heba Waly via GitGitGadget
2019-10-24 20:48       ` Emily Shaffer

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=pull.412.v2.git.1571815556.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=heba.waly@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).