From: khamis2@t-online.de (Khamis Abuelkomboz)
To: irox@sbcglobal.net
Cc: sourcenav@sources.redhat.com
Subject: Re: Back online...
Date: Sun, 07 Apr 2002 16:13:00 -0000 [thread overview]
Message-ID: <3CB0D2A8.7020605@t-online.de> (raw)
In-Reply-To: <20020406123236.6aae8802.irox@sbcglobal.net>
Hi Ian,
welcome you back. hopefully you enjoy the time in santa cruz.
Since you left redhat, is there anybody who still deal with SN in redhat
(Mo)?
As you see, I packaged all my stuff and released SN50E. It contains
the bug fixes, parsers and the gui rework to SN50. I think, this is a
good base
to start from. We kann put all the stuff on SourceForge and continue
developing SN. This in relation with the question, if redhat will allow
us to have access to the SN-cvs tree?
The CVS Tree contains Tcl/Tk8.3 and SN50 is released with Tcl/Tk8.1.
My question here, do we need to always upgrade to the newest tcl/tk
release? Because upgrading takes the most time and since we do not
have alot of time to work on SN, the benefit will go to improve SN.
Khamis
irox@sbcglobal.net wrote:
>Hi all,
>
>Sorry about my unannounced absence for the last month
>or so. I no longer work for Red Hat and I moved to
>Santa Cruz, then had to fight with SBC to turn on my
>DSL line (the longest block of time I gone without
>internet access since the early 90s...).
>
>
>The first thing I'd like to talk about is Copyright
>assignments. While I was still working for RH I
>brought the idea of making Source-Navigator a
>multi-copyright holder project to as many people in
>RH as I could. This would mean people who contribute
>code to Source-Navigator don't have to sign over thier
>copyrights to Red Hat. I was never able to get a firm
>yes or no from anybody, but I would like to implement
>this (long over due) change anyway.
>
>
>What's happening with "libSN" (or whatever it was called)?
>I'd prefer to wait until there is something to show before
>creating a CVS modules for it.
>
>
>Anyway, with contributions from Khamis, Mo and myself
>we should be able turn out a new SN release. At somepoint
>I'll go over the last month or so of the mailing list and
>apply any patches I've missed, reply to any interesting
>emails, etc..
>
>Thanks for your patience,
>and a big thanks to everybody who answered email
>on this list over the last month. :-)
>
>Ian.
>
>
--
--
Dipl.-Informatiker
Khamis Abuelkomboz
Rosenweg 124
58239 Schwerte
+49 2304 898560 (Telefon)
+49 2304 898561 (Fax)
http://khamis.oimanager.de
next prev parent reply other threads:[~2002-04-07 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 11:17 irox
2002-04-07 16:13 ` Khamis Abuelkomboz [this message]
2002-04-08 16:04 ` Mo DeJong
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=3CB0D2A8.7020605@t-online.de \
--to=khamis2@t-online.de \
--cc=irox@sbcglobal.net \
--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).