All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "skrab-sah via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, skrab-sah <skrab.sah@gmail.com>
Subject: Re: [PATCH] abspath.h is created.
Date: Tue, 27 Sep 2022 17:40:58 -0700	[thread overview]
Message-ID: <xmqq8rm41gbp.fsf@gitster.g> (raw)
In-Reply-To: pull.1345.git.git.1664294909011.gitgitgadget@gmail.com

"skrab-sah via GitGitGadget" <gitgitgadget@gmail.com> writes:

> diff --git a/abspath.h b/abspath.h
> new file mode 100644
> index 00000000000..edebc3a53ba
> --- /dev/null
> +++ b/abspath.h
> @@ -0,0 +1,9 @@
> +/* \aThis file was automatically generated.  Do not edit! */

No thanks.

I suspect this change is taking us in a wrong direction.  People
grep for function and struct declarations in <*.h> files and expect
to find the associated comments.

  reply	other threads:[~2022-09-28  0:41 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 [this message]
2022-09-28  7:32   ` Skrab Sah
2022-09-28 15:39     ` Taylor Blau
2022-09-28 17:58     ` Junio C Hamano

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=xmqq8rm41gbp.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.