From: "Frank Ch. Eigler" <fche@elastic.org>
To: overseers@sourceware.org
Subject: Re: src/winsup/cygwin common.din syscalls.cc inclu ...
Date: Mon, 13 Oct 2014 13:01:00 -0000 [thread overview]
Message-ID: <20141013130103.GA26694@elastic.org> (raw)
In-Reply-To: <20141013125439.GA29824@calimero.vinschen.de>
Hi -
On Mon, Oct 13, 2014 at 02:54:39PM +0200, Corinna Vinschen wrote:
> [...]
> > > It'd be nice to change the cvs hooks (?) to generate direct
> > > viewvc URLs too sometime.
> >
> > How can we do that? Where is this configured?
>
> Is that something we can do at all without overseers intervention?
On brief searching, it seems like a matter for overseers:
/sourceware/infra/bin/log_accum
- FChE
next prev parent reply other threads:[~2014-10-13 13:01 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 [this message]
2014-10-17 15:54 ` Corinna Vinschen
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=20141013130103.GA26694@elastic.org \
--to=fche@elastic.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).