From: Ian Lance Taylor <ian@wasabisystems.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: overseers@gcc.gnu.org
Subject: Re: can't commit to 3.3-e500
Date: Wed, 11 Feb 2004 14:24:00 -0000 [thread overview]
Message-ID: <m3n07p3d9f.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040211141556.GA3575@redhat.com>
Aldy Hernandez <aldyh@redhat.com> writes:
> Can someone take a look at this?
>
> Aldy
>
> Checking in ChangeLog.e500;
> /cvsroot/gcc/gcc/gcc/Attic/ChangeLog.e500,v <-- ChangeLog.e500
> new revision: 1.1.2.35; previous revision: 1.1.2.34
> cvs [server aborted]: could not open lock file `/cvsroot/gcc/gcc/gcc/Attic/,ChangeLog.e500,': Permission denied
> cvs commit: saving log message in /tmp/cvsHL52RT
Everything looks fine to me. You are in the right group, permissions
are OK, the file does not exist. Did somebody else fix it already?
Does this happen consistently? What is in your CVS/Root file?
Ian
next prev parent reply other threads:[~2004-02-11 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 14:15 Aldy Hernandez
2004-02-11 14:24 ` Ian Lance Taylor [this message]
2004-02-11 15:08 ` Aldy Hernandez
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=m3n07p3d9f.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=aldyh@redhat.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).