Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <0fc101c1454a$aa8b8010$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <0db601c144fe$3ec53ca0$0200a8c0 AT lifelesswks> <20010924170130 DOT B31556 AT redhat DOT com> <0f5701c14546$0bd99280$0200a8c0 AT lifelesswks> <20010924183659 DOT B32477 AT redhat DOT com> Subject: Re: CVS branches RFC Date: Tue, 25 Sep 2001 08:45:52 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 24 Sep 2001 22:53:46.0145 (UTC) FILETIME=[C44ED910:01C1454B] ----- Original Message ----- From: "Christopher Faylor" > I don't think that I really have the authority to allow people to > create branches in newlib. Maybe we should get permission from > newlib AT sources DOT redhat DOT com before creating branches there. newlibs not _really_ essential, as changes occur relatively rarely there, I'm just making sure I don't cause havoc :}. If I call cvs -z9 -q rtag -r HEAD -b foo src/winsup cvs -z9 -q rtag -r foo Z-foo_merge_HEAD src/winsup from within winsup in a checked out sources repository, will that be ok? (ie will that avoid affecting newlib). > Should we create another directory in winsup for dealing with > these kind of things like "winsup/scripts" or "winsup/maint"? maint sounds good - room for other things too. If it's ok, I'll upload the scripts for folk to have a look at. Rob