public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] Git et al
Date: Mon, 04 Aug 2014 21:41:00 -0000	[thread overview]
Message-ID: <20140804214106.GA21621@dinwoodie.org> (raw)
In-Reply-To: <20140721074553.GA4682@dinwoodie.org>

On Mon, Jul 21, 2014 at 08:45:53AM +0100, Adam Dinwoodie wrote:
> > I have been using git 2.0.2 that I built myself for a while now, so I
> > tried this command using my copy. FWIW, the import works just fine with
> > my x86_64 build, but fails with the same messages you get with the i686
> > build.
> 
> That's odd!  I'll try to replicate that myself, but assuming I see the
> same behaviour, that implies there's something going wrong that's
> probably beyond my ability to debug with the time I can spare.
> 
> That said, if the 64-bit version works, and assuming nobody here
> objects, I'll suggest releasing that 2.0.2 build and just highlighting
> the bug in the release email, and suggesting using the 64-bit build for
> folk affected by the bug.
> 
> I'll be back at my own computer later this week, so I should be able to
> rebuild and test properly either this week or next.

Just to update folk: I've bumped to v2.0.4, and everything's working a
lot more nicely.  I've managed CVS imports using both 32-bit and 64-bit,
and I'm in the process of ironing out a few kinks in the test suites
before I'm ready to release.

This definitely feels like the home stretch for getting something ready
to upload and distribute.

  reply	other threads:[~2014-08-04 21:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 20:02 Adam Dinwoodie
2014-01-11 20:04 ` Adam Dinwoodie
2014-01-13  9:25 ` Corinna Vinschen
2014-01-13 21:32 ` Eric Blake
2014-01-13 23:59   ` Adam Dinwoodie
2014-01-15 11:06     ` Adam Dinwoodie
2014-01-17 18:42       ` Balaji Venkataraman
2014-01-17 18:48         ` Christopher Faylor
2014-01-17 22:58           ` Balaji Venkataraman
2014-01-24 14:25       ` Eric Blake
2014-01-29 11:53         ` Adam Dinwoodie
2014-01-29 16:54           ` Yaakov (Cygwin/X)
2014-01-29 17:07             ` Adam Dinwoodie
2014-01-30 10:00               ` Yaakov (Cygwin/X)
2014-01-29 17:45             ` Achim Gratz
2014-01-29 19:33               ` Jan Nijtmans
2014-01-29 19:56                 ` Achim Gratz
2014-06-10 22:00 ` Yaakov Selkowitz
2014-06-10 22:36   ` Adam Dinwoodie
2014-06-11  3:55     ` Achim Gratz
2014-06-11  4:23       ` Achim Gratz
2014-06-11  4:20     ` Yaakov Selkowitz
2014-07-19  7:29       ` Adam Dinwoodie
2014-07-19 13:54         ` Christopher Faylor
2014-07-19 23:47         ` David Rothenberger
2014-07-21  7:46           ` Adam Dinwoodie
2014-08-04 21:41             ` Adam Dinwoodie [this message]
2014-08-13 19:12               ` Adam Dinwoodie
2014-08-13 19:37                 ` Eric Blake
2014-08-15  4:25                   ` Eric Blake
2014-08-15  4:46                     ` Marco Atzeri
2014-08-15  8:25                     ` Adam Dinwoodie
2014-08-15  8:31                       ` Adam Dinwoodie
2014-08-15  7:05                 ` Yaakov Selkowitz
2014-08-20 20:19                   ` Adam Dinwoodie
2014-08-20 22:19                     ` Yaakov Selkowitz
2014-08-18 18:38                 ` Eric Blake
2014-09-21 12:57                   ` Andrew Schulman

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=20140804214106.GA21621@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin-apps@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).