public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: [Attn CVS maintainer] Re: CVS checkout with absolute path fails in 32-bit build
Date: Mon, 27 Jul 2015 22:48:00 -0000	[thread overview]
Message-ID: <20150727224756.GM14466@dinwoodie.org> (raw)
In-Reply-To: <55AEB9BD.1030705@gmail.com>

On Tue, Jul 21, 2015 at 11:29:33PM +0200, Marco Atzeri wrote:
> I just uploaded a cvs-1.11.23-2 version as test for 32bit only.

I missed the "as test" the first time I read this email, and thought all
my mirrors were being incredibly slow to pick up the change...

> It uses all the patches available in Fedora.
> 
> cvs-1.11.23-1 patches were not enough due to some change in
> info building.
> 
> Could you check if does it solve your problem ?

I've just confirmed: with cvs 1.11.23-2, t9200 of the Git test suite is
passing just fine on 32-bit Cygwin.

Thanks!

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

  parent reply	other threads:[~2015-07-27 22:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 19:09 Adam Dinwoodie
2015-07-18 11:37 ` [Attn CVS maintainer] " Adam Dinwoodie
2015-07-20  9:48   ` Corinna Vinschen
2015-07-20  9:59     ` Corinna Vinschen
2015-07-20 10:03     ` Marco Atzeri
2015-07-20 11:23       ` Corinna Vinschen
2015-07-20 11:27       ` Adam Dinwoodie
2015-07-20 11:36         ` Achim Gratz
2015-07-20 11:57           ` Git packages with Perl 5.2.2 [Was: CVS checkout with absolute path fails in 32-bit build] Adam Dinwoodie
2015-07-21 21:29         ` [Attn CVS maintainer] Re: CVS checkout with absolute path fails in 32-bit build Marco Atzeri
2015-07-21 23:28           ` Adam Dinwoodie
2015-07-27 22:48           ` Adam Dinwoodie [this message]
2015-07-28  7:41             ` Marco Atzeri

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=20150727224756.GM14466@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.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).