Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Wed, 11 Jul 2001 12:30:13 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: resedit CVS module created
Message-ID: <20010711123013.G30170@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF7A1A AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF7A1A@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Tue, Jul 10, 2001 at 05:13:36PM +1000

Robert has pointed out to me in private email that there is an
annoying problem with this repository.  I meant to fix it before
I left on vacation but I forgot.

If you check something into the cygwin-apps repository, you'll
get a usage message from the qmail system on sources.redhat.com.

The reason for this is that cvs expects that there is a 'cygwin-apps-cvs'
mailing list for checkin notifications.  There isn't.  So, you will
get an error on each commit.

I apologize for the inconvenience.  I'll fix it when I return.

cgf

On Tue, Jul 10, 2001 at 05:13:36PM +1000, Robert Collins wrote:
>I've created a new module "resedit" on the
>sources.redhat.com:/cvs/cygwin-apps cvs repository. 
>
>Thanks for the space Chris!
>
>It contains version 0.1 of resedit, a GPL'd win32 rc file editor. At
>this point in time it can parse an rc file and display a tree view of
>the found resources. The next step is to extend the original binutils
>code to allow writing a valid .rc file, and then we are onto actual
>editing!.
>
>Anyone who wishes to is welcome to join in. As usual for open
>development projects, those dallying will need to send in patches, those
>interested in actively developing the code can get write access.
>
>Whilst this is a low priority for me, I'm aiming to hit milestones every
>month or so, just to keep things moving along.
>
>Rob

-- 
cgf AT cygnus DOT com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/