From: Mark Wielaard <mark@klomp.org>
To: Mark Wielaard via Overseers <overseers@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
Tobias Burnus <tobias@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: git safe.directory
Date: Tue, 23 May 2023 10:41:34 +0200 [thread overview]
Message-ID: <20230523084134.GA24812@gnu.wildebeest.org> (raw)
In-Reply-To: <ceb5a0dad8e9dbe96912cbd9a11e74d46a37277a.camel@klomp.org>
Hi,
On Mon, May 22, 2023 at 06:13:37PM +0200, Mark Wielaard via Overseers wrote:
> I missed the gcc-wwwdocs post-receive hook.
> Tobias noticed that commits don't update the website anymore.
> And the /www/gcc/update.log do indeed contains:
> fatal: detected dubious ownership in repository at
> '/sourceware1/www/gcc/wwwdocs-checkout'
>
> For now I have added as a workaround to /etc/gitconfig:
>
> [safe]
> directory = /sourceware1/www/gcc/wwwdocs-checkout
>
> Which should make it possible for anybody to run the post-receive hook
> again. But I think it would be better if we change things so that only
> gccadmin (who owns the wwwdocs-checkout repo) would do the updates
> (from a cronjob?)
>
> Note, I didn't try to replay the last few failing commits, so someone
> should still do that to get the gcc.gnu.org website updated.
I now looked and processed the following 3 commits, which didn't auto
update:
commit 4013044e02d0b04430531bb604ddb201c51cb238
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon May 22 10:49:27 2023 +0200
Mention 11 branch is frozen.
commit 6196747803d192744097590d6703a94def0030f4
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon May 22 10:08:14 2023 +0200
git.html: Move OG12 to OG13, briefly mention old branches
commit fd86c2b52a4fa69ac5a7755b55934c6a9c3e7cd7
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Sun May 21 20:40:19 2023 +0200
readings: Adjust link to Arm architectures
Which effectively was just calling /www/gcc/bin/preprocess on
readings.html, git.html and index.html.
Cheers,
Mark
prev parent reply other threads:[~2023-05-23 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 17:21 Mark Wielaard
2023-05-22 16:13 ` Mark Wielaard
2023-05-23 8:41 ` Mark Wielaard [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=20230523084134.GA24812@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=brobecker@adacore.com \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=jwakely.gcc@gmail.com \
--cc=overseers@sourceware.org \
--cc=tobias@codesourcery.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).