X-Spam-Check-By: sourceware.org
Date: Wed, 23 Nov 2005 12:34:19 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Enscript error with passwd uid field (enscript-1.6.3-3)
Message-ID: <20051123113419.GB8644@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OF609EEA81 DOT F5085C04-ONC12570C2 DOT 0039B83F-C12570C2 DOT 003B1DED AT philips DOT com> <43845104 DOT 7CF4126D AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43845104.7CF4126D@dessent.net>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Nov 23 03:22, Brian Dessent wrote:
> It looks like preliminary support for 32 bit uid_t began around
> 2002-02-09:
> <http://www.cygwin.com/ml/cygwin-cvs/2002-q1/msg00131.html>.  The
> release notes for 1.3.11 mentions this as well on 2002-05-23:
> <http://www.cygwin.com/ml/cygwin-announce/2002-06/msg00012.html>.  I
> don't know when "the switchover" actually happened and uid_t actually
> officially became unsigned long.

With 1.5.0, whenever that was :-)


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/