From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: Re: src/winsup/cygwin common.din syscalls.cc inclu ...
Date: Fri, 17 Oct 2014 15:54:00 -0000 [thread overview]
Message-ID: <20141015073512.GA32216@calimero.vinschen.de> (raw)
In-Reply-To: <20141009115017.GA20741@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hi,
On Oct 9 13:50, Corinna Vinschen wrote:
> On Oct 9 06:09, Frank Ch. Eigler wrote:
> > Hi -
> >
> > > It looks like things recently changed on sourceware so that the links in
> > > these emails no longer work.
> > > [...]
> > > > Patches:
> > > > http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/common.din.diff?cvsroot=src&r1=1.9&r2=1.10
> >
> > Sorry about that; a while ago when a yet another security
> > vulnerability in cvsweb.cgi came by, it seemed harmless to switch it
> > out for (redirect to) the other cvs-viewer platform already installed
> > on sourceware. I did not know about this usage, so the redirection
> > part wasn't sophisticated enough.
> >
> > I'll tweak the forwarding regex widget to make those URLs work, if
> > possible.
>
> Seems to work fine now, thanks!
The CVS mails from the cygwin-apps repo are affected as well, apparently.
For instance, this link given in a mail on the cygwin-apps-cvs mailing
list:
http://sourceware.org/cgi-bin/cvsweb.cgi/login/login.1.diff?cvsroot=cygwin-apps&r1=1.1.1.1&r2=1.2
now redirects to
https://sourceware.org/viewvc/src/
Can this be fixed, please?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-15 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141008210341.20952.qmail@sourceware.org>
2014-10-09 3:28 ` Eric Blake
2014-10-09 10:09 ` Frank Ch. Eigler
2014-10-09 11:50 ` Corinna Vinschen
2014-10-13 12:54 ` Corinna Vinschen
2014-10-13 13:01 ` Frank Ch. Eigler
2014-10-17 15:54 ` Corinna Vinschen [this message]
2014-10-20 5:36 ` Frank Ch. Eigler
2014-10-20 14:11 ` Corinna Vinschen
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=20141015073512.GA32216@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).