From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
libffi-discuss@sourceware.org,
Java Patches <java-patches@gcc.gnu.org>,
Rainer Emrich <rainer@emrich-ebersheim.de>
Subject: Re: [PATCH] Fix Cygwin bootstrap, PR40807 and all significant FAILs on win32.
Date: Fri, 24 Jul 2009 10:14:00 -0000 [thread overview]
Message-ID: <4A698C7B.5050507@gmail.com> (raw)
In-Reply-To: <4A697AF2.8040900@redhat.com>
Andrew Haley wrote:
> Yes.
>
> Andrew.
I believe this means I don't have write privs to the sourceware:/libffi
repository:
> $ cvs ci src/x86/ffi.c src/x86/win32.S src/closures.c ChangeLog
> Enter passphrase for key '/home/DKAdmin/.ssh/id_rsa':
> Checking in src/x86/ffi.c;
> /cvs/libffi/libffi/src/x86/ffi.c,v <-- ffi.c
> new revision: 1.17; previous revision: 1.16
> cvs [commit aborted]: could not open lock file `/cvs/libffi/libffi/src/x86/,ffi.c,': Permission denied
> cvs commit: saving log message in /tmp/cvs0JL83Z
... so I've applied it to GCC SVN only so far; can you or Tim copy it over?
(Or priv me up and I'll do it.)
cheers,
DaveK
next prev parent reply other threads:[~2009-07-24 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:30 Dave Korn
2009-07-22 20:12 ` [PATCH] Fix Cygwin bootstrap, PR40807 and all significant *libffi* " Dave Korn
2009-07-23 10:16 ` [PATCH] Fix Cygwin bootstrap, PR40807 and all significant " Andrew Haley
2009-07-23 10:20 ` Dave Korn
2009-07-24 3:08 ` Dave Korn
2009-07-24 9:12 ` Andrew Haley
2009-07-24 10:14 ` Dave Korn [this message]
2009-07-23 10:51 ` Timothy Wall
2009-07-23 11:03 ` Dave Korn
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=4A698C7B.5050507@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.org \
--cc=rainer@emrich-ebersheim.de \
/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).