From: Joseph Myers <joseph@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jakub Jelinek <jakub@redhat.com>, <overseers@gcc.gnu.org>,
Richard Guenther <richard.guenther@gmail.com>
Subject: Re: Updates of wwwdocs not working anymore
Date: Sat, 11 Jan 2020 21:09:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2001112109050.30962@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LSU.2.21.2001112120490.3725@anthias.pfeifer.com>
On Sat, 11 Jan 2020, Gerald Pfeifer wrote:
> I'll admit this is a bit over my head. We just ran into this again,
> though, so would you mind having a look?
>
> To be clear, /www/gcc/htdocs-preformatted (the raw checkout from git)
> features -rw-r--r-- for most files which seems to be fine, though, and
> does not cause problems. It's the pre-processed web tree under
> /www/gcc/htdocs where this hits.
>
> Maybe setting a more permissive umask before invoking
> /www/gcc/bin/preprocess is the best approach?
I've applied a change that both sets a umask and explicitly removes
destination files before copying over them (so as to be unaffected by
their permissions).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-01-11 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191129150340.13533.qmail@sourceware.org>
[not found] ` <20191129150345.CEE2933E0E@hamza.pair.com>
[not found] ` <20191129154410.GN10088@tucnak>
2019-11-29 16:38 ` Gerald Pfeifer
2019-11-29 17:11 ` Joseph Myers
2020-01-11 20:37 ` Gerald Pfeifer
2020-01-11 21:09 ` Joseph Myers [this message]
2020-01-19 15:07 ` Gerald Pfeifer
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=alpine.DEB.2.21.2001112109050.30962@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=richard.guenther@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 read-only IMAP folder(s) and NNTP newsgroup(s).