From: Gerald Pfeifer <gerald@pfeifer.com>
To: Joseph Myers <joseph@codesourcery.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: Sun, 19 Jan 2020 15:07:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.2001191606060.739@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2001112109050.30962@digraph.polyomino.org.uk>
On Sat, 11 Jan 2020, Joseph Myers wrote:
> 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).
Thank you, Joseph!
From the experience of the last week, where several of us updated
the same file in wwwdocs it appears this resolved the issue.
Gerald
prev parent reply other threads:[~2020-01-19 15:07 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
2020-01-19 15:07 ` Gerald Pfeifer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.21.2001191606060.739@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).