From: Ian Roxborough <irox@redhat.com>
To: sourcenav@sources.redhat.com, sourcenav@sourceware.cygnus.com
Subject: Re: Patches...[was: Re: SourceNav release ...
Date: Tue, 08 Jan 2002 12:51:00 -0000 [thread overview]
Message-ID: <20020108124411.5ac56b94.irox@redhat.com> (raw)
Hi Bernard,
thanks for pointing that out, I've removed the requirement
to run frink for the time being and updated the webpage
to reflect this.
Ian.
On Tue, 8 Jan 2002 14:15:27 +0100 Bernard Dautrevaux <Dautrevaux@microprocess.com> wrote:
> > It's here and always was:
> > http://sources.redhat.com/sourcenav/contrib.html
> >
> > It was already there (scroll down to "Submitting Patches").
>
> Fine page; only problem: it says we must format tcl/tk code with frink, as
> you've modified it to accept [incr tcl]. It seems perfectly reasonable...
> except almost nobody can download this version of frink, as the ftp server
> on source.redhat.com is restricted (AFAICR only mirrors are able to get to
> source.redhat.com in FTP due to load problems).
>
> So where could we get this "frink" tcl/tk formatter that seems mandatory to
> provide patches to the current snapshots/CVS version of SN?
>
> Regards,
>
> Bernard
>
> --------------------------------------------
> Bernard Dautrevaux
> Microprocess Ingenierie
> 97 bis, rue de Colombes
> 92400 COURBEVOIE
> FRANCE
> Tel: +33 (0) 1 47 68 80 80
> Fax: +33 (0) 1 47 88 97 85
> e-mail: dautrevaux@microprocess.com
> b.dautrevaux@usa.net
> --------------------------------------------
WARNING: multiple messages have this Message-ID
From: Ian Roxborough <irox@redhat.com>
To: sourcenav@sources.redhat.com, sourcenav@sourceware.cygnus.com
Subject: Re: Patches...[was: Re: SourceNav release ...
Date: Wed, 09 Jan 2002 10:54:00 -0000 [thread overview]
Message-ID: <20020108124411.5ac56b94.irox@redhat.com> (raw)
Message-ID: <20020109105400.iOdiCAzIHT540sh8HPTM4KlUvGmVYl0ANP9DCe3f0sg@z> (raw)
Hi Bernard,
thanks for pointing that out, I've removed the requirement
to run frink for the time being and updated the webpage
to reflect this.
Ian.
On Tue, 8 Jan 2002 14:15:27 +0100 Bernard Dautrevaux <Dautrevaux@microprocess.com> wrote:
> > It's here and always was:
> > http://sources.redhat.com/sourcenav/contrib.html
> >
> > It was already there (scroll down to "Submitting Patches").
>
> Fine page; only problem: it says we must format tcl/tk code with frink, as
> you've modified it to accept [incr tcl]. It seems perfectly reasonable...
> except almost nobody can download this version of frink, as the ftp server
> on source.redhat.com is restricted (AFAICR only mirrors are able to get to
> source.redhat.com in FTP due to load problems).
>
> So where could we get this "frink" tcl/tk formatter that seems mandatory to
> provide patches to the current snapshots/CVS version of SN?
>
> Regards,
>
> Bernard
>
> --------------------------------------------
> Bernard Dautrevaux
> Microprocess Ingenierie
> 97 bis, rue de Colombes
> 92400 COURBEVOIE
> FRANCE
> Tel: +33 (0) 1 47 68 80 80
> Fax: +33 (0) 1 47 88 97 85
> e-mail: dautrevaux@microprocess.com
> b.dautrevaux@usa.net
> --------------------------------------------
next reply other threads:[~2002-01-08 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 12:51 Ian Roxborough [this message]
2002-01-09 10:54 ` Ian Roxborough
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=20020108124411.5ac56b94.irox@redhat.com \
--to=irox@redhat.com \
--cc=sourcenav@sources.redhat.com \
--cc=sourcenav@sourceware.cygnus.com \
/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).