From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: chown -R gccadmin /www/gcc/htdocs-preformatted
Date: Tue, 18 Oct 2022 10:46:35 -0400 [thread overview]
Message-ID: <20221018144635.GC10311@redhat.com> (raw)
In-Reply-To: <f8a14896-4b4d-0086-6b69-863d32932180@pfeifer.com>
Hi -
> Martin reported that his latest change to
> https://gcc.gnu.org/codingconventions.html
> did not make it to the actual gcc.gnu.org site after pushing to git.
> [...]
> Updating 68c7552f..415fcf49
> error: unable to unlink old 'htdocs/onlinedocs/8.4.0/index.html': Permission denied
This is fixed via chown and a few strategic chmod g+ws's.
> [...]
> And then see whether
> cd /www/gcc/htdocs-preformatted ; git pull
> (as user gccadmin) succeeds?
No, because git pull fails with a different error (extra commits on
local master vs. origin/master branch). I think you are able to
clean that up without more fuss.
By the way, other projects use git-backed htdocs here with less
machinery, where in a commit to the FOO-htdocs git repo automatically
checks things out to a htdocs directory, sans manual/gccadmin
intervention. Consider.
- FChE
prev parent reply other threads:[~2022-10-18 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:15 Gerald Pfeifer
2022-10-18 14:46 ` Frank Ch. Eigler [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=20221018144635.GC10311@redhat.com \
--to=fche@redhat.com \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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).