public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1750] .gitignore: do not ignore config.h
Date: Tue, 19 Jul 2022 14:07:31 +0000 (GMT)	[thread overview]
Message-ID: <20220719140731.3857E3858439@sourceware.org> (raw)

https://gcc.gnu.org/g:4a8aab9a23550dbf53d4640fef57c0bd6f6b0129

commit r13-1750-g4a8aab9a23550dbf53d4640fef57c0bd6f6b0129
Author: Alexander Monakov <amonakov@ispras.ru>
Date:   Tue Jul 19 16:37:04 2022 +0300

    .gitignore: do not ignore config.h
    
    GCC does not support in-tree builds at the moment, so .gitignore
    concealing artifacts of accidental in-tree ./configure run may cause
    confusion. Un-ignore config.h, which is known to break the build.
    
    ChangeLog:
    
            * .gitignore: Do not ignore config.h.

Diff:
---
 .gitignore | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.gitignore b/.gitignore
index 021a8c74185..5cc4a0fdfa6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -23,7 +23,8 @@
 
 autom4te.cache
 config.cache
-config.h
+# GCC does not support in-tree builds, do not conceal a stray config.h:
+# config.h
 config.intl
 config.log
 config.status


                 reply	other threads:[~2022-07-19 14:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220719140731.3857E3858439@sourceware.org \
    --to=amonakov@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).