public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. b3ed2d817de659c08c6e33f8aaf94c337fca13f2
Date: Fri, 19 May 2023 14:00:31 +0000 (GMT)	[thread overview]
Message-ID: <20230519140031.85B96385771F@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  b3ed2d817de659c08c6e33f8aaf94c337fca13f2 (commit)
      from  553eb2f76d6414e962f923c3bacf33edd0040491 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b3ed2d817de659c08c6e33f8aaf94c337fca13f2
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri May 19 15:59:46 2023 +0200

    preprocess: Fix reference to SOURCETREE

diff --git a/bin/preprocess b/bin/preprocess
index c6d34c4b..2e474b0c 100755
--- a/bin/preprocess
+++ b/bin/preprocess
@@ -155,7 +155,7 @@ process_file()
     # Strip possibly leading "./".
     f=`echo $1 | sed -e 's#^\./##'`
 
-    if [ ! -f "$SRCTREE/$f" ]; then
+    if [ ! -f "$SOURCETREE/$f" ]; then
         echo "Input file $f not found."
         return
     fi

-----------------------------------------------------------------------

Summary of changes:
 bin/preprocess | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-05-19 14:00 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=20230519140031.85B96385771F@sourceware.org \
    --to=gerald@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).