public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Bernard Dautrevaux <Dautrevaux@microprocess.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Patches...[was: Re: SourceNav release ... ]
Date: Wed, 09 Jan 2002 14:22:00 -0000	[thread overview]
Message-ID: <20020109112154.0e3e503a.irox@redhat.com> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E40F@IIS000>


Hi,

This is the version of frink that I hacked to work with
Itcl3.0 code:

http://people.redhat.com/irox/frink/frink-1.2p40-itcl3.tar.gz

I did this work against frink version 1.2 and then version
2.0 came out and I didn't have enough time to move my changes
into the 2.0 version and submit them back.

There is still no requirement to run frink on your code
before submitting a patch.  Frink was mainly used for us
to unify the coding style (as SN has had many different
developers using different coding styles in the past).

Ian.

On Wed, 9 Jan 2002 10:14:31 +0100  Bernard Dautrevaux <Dautrevaux@microprocess.com> wrote:
>
> > -----Original Message-----
> > From: Ian Roxborough [mailto:irox@redhat.com]
> > Sent: Tuesday, January 08, 2002 9:27 PM
> > To: Dautrevaux@microprocess.com
> > Cc: sourcenav@redhat.com
> > Subject: Re: Patches...[was: Re: SourceNav release ... ]
> > 
> > 
> > 
> > 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.
> > 
> 
> Frink looking like a nice tool for this purpose, couldn't the itcl-aware
> version be either contributed to the original frink (if the fact that I
> can't even doanload it through your link is just a temporary situation), or
> proposed as an html download or at least though CVS?
> 
> TIA
> 
> 	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
> -------------------------------------------- 

       reply	other threads:[~2002-01-09 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17B78BDF120BD411B70100500422FC6309E40F@IIS000>
2002-01-09 14:22 ` Ian Roxborough [this message]
2002-01-08  5:24 Bernard Dautrevaux
  -- strict thread matches above, loose matches on Subject: below --
2002-01-06  0:26 SourceNav release Simonovsky, Pavel
2002-01-06  3:48 ` Mo DeJong
2002-01-06  6:36   ` Ralf Corsepius
2002-01-07 13:22     ` Ian Roxborough
2002-01-07 13:34       ` Patches...[was: Re: SourceNav release ... ] 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=20020109112154.0e3e503a.irox@redhat.com \
    --to=irox@redhat.com \
    --cc=Dautrevaux@microprocess.com \
    --cc=sourcenav@sources.redhat.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).