From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Gerald Pfeifer" <gerald@pfeifer.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Some problems with the GCC web machinery
Date: Sun, 20 May 2007 22:56:00 -0000 [thread overview]
Message-ID: <4aca3dc20705201556pf70bddan38489a71511b58c1@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705202336250.26010@acrux.dbai.tuwien.ac.at>
On 5/20/07, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Based on a report by Uros I investigated and found that
> /www/gcc/htdocs-preformatted had not been automatically updated for
> the latest sets of changes:
>
> I know did this manually...
>
> [gerald@sourceware htdocs-preformatted]$ cvs -q up -PAd
> U gcc-4.3/changes.html
> U gcc-4.3/cxx0x_status.html
>
> ...and also invoked /www/gcc/bin/preprocess to push the changes from
> there to /www/gcc/htdocs and thus the web server but wonder whether any
> of you may have an idea on might have gone wrong? This system has not
> seen any changes (that I would know of) for a while, so I cannot explain
> what may have caused this.
>
>
> On a (possibly, but probably not) related note, I found the following
> permissions under /www/gcc which break a `cvs up` at that level of the
> tree:
>
> drwxr-sr-x 13 dberlin gcc 4096 Mar 13 15:00 bugzilla
> drwxr-sr-x 2 dberlin gcc 4096 Nov 8 2003 bzCVS
> drwxr-sr-x 2 dberlin gcc 4096 Aug 31 2005 wikiconfig
> drwxrwxr-x 13 dberlin apache 4096 Jul 25 2005 wikidata
>
> Daniel, did you look these down intentionally, are could you make these
> tree group writable?
>
I certainly don't remember doing this, feel free to chmod g+w them
> Gerald
>
next prev parent reply other threads:[~2007-05-20 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 22:51 Gerald Pfeifer
2007-05-20 22:56 ` Daniel Berlin [this message]
2007-05-21 2:46 ` Gerald Pfeifer
2007-05-21 9:00 ` Benjamin Kosnik
2007-05-27 12:40 ` 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=4aca3dc20705201556pf70bddan38489a71511b58c1@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=gerald@pfeifer.com \
--cc=overseers@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).