git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Skrab Sah <skrab.sah@gmail.com>
Cc: skrab-sah via GitGitGadget <gitgitgadget@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] abspath.h is created.
Date: Wed, 28 Sep 2022 10:58:49 -0700	[thread overview]
Message-ID: <xmqqpmfftm7a.fsf@gitster.g> (raw)
In-Reply-To: <CA+J78MXbXG4M1w50EAM8t0VkYP_saCt9O90jFKad3+cB+RCZ-Q@mail.gmail.com> (Skrab Sah's message of "Wed, 28 Sep 2022 13:02:22 +0530")

Skrab Sah <skrab.sah@gmail.com> writes:

> What is wrong here and what should i do to make it correct.

Almost everything in what the patch is wrong.

 * It creates <abspath.h> as a tracked file, but has a funny comment
   with control-G in it that says "do not edit"

 * It is entirely unclear how the contents of <abspath.h> is meant
   to evolve, if the contributors are forbidden to edit it, and
   without any instruction how to update it.

 * The new <abspath.h> lost all function comments, grouping by
   category, etc. that were in the original <cache.h>.

 * There is an "#undef INTERFACE" that has no use to us, those who
   develop Git, for no clearly explained reason.

 * The proposed log message says what it did, but it does not even
   try to justify why it is a good idea to do so.

 * There is no need to create a new <abspath.h> in the first place.
   If we were in an alternate world where we did not have
   <abspath.c>, it may be reasonable to add <abspath.h> along with
   it, instead of adding declarations for new functions and types in
   <cache.h>.  But the difference falls into "once it is in, it is
   not worth the patch churn to change it" category.

The easiest way to make it correct is to drop it, I guess.

Thanks.


      parent reply	other threads:[~2022-09-28 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:08 [PATCH] abspath.h is created skrab-sah via GitGitGadget
2022-09-28  0:40 ` Junio C Hamano
2022-09-28  7:32   ` Skrab Sah
2022-09-28 15:39     ` Taylor Blau
2022-09-28 17:58     ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpmfftm7a.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=skrab.sah@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).