public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Gilbert <david.gilbert@object-refinery.com>
To: audriusa@bluewin.ch
Cc: Martin Olsson <mnemo@minimum.se>, mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Sat, 10 Sep 2005 07:59:00 -0000	[thread overview]
Message-ID: <4322A084.8010802@object-refinery.com> (raw)
In-Reply-To: <43228CB8.2060305@bluewin.ch>

Meskauskas Audrius wrote:

> Of course, it is worthwhile to learn how to to run a complete Mauve 
> test set, and how to build Classpath, and join the main project 
> developing and so on. All this would be great from your side, but it 
> takes time and may not be easy under Windows. 


It won't be easy to run all the tests on Windows initially, but I think 
if we can solve the problem of checking out the CVS into Eclipse on 
Windows, it won't be long before someone writes a utility to make it 
simple to compile and run all (or a selected subset of) the tests.  And 
if the end result is more developers working on Mauve, then I think it 
is worth the effort.

Regards,

Dave

  reply	other threads:[~2005-09-10  7:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 18:58 Martin Olsson
2005-09-09 20:01 ` Meskauskas Audrius
2005-09-09 23:54   ` Martin Olsson
2005-09-10  7:35     ` Meskauskas Audrius
2005-09-10  7:59       ` David Gilbert [this message]
2005-09-10  9:30         ` Mauve coding on Windows: The majority of tests runs under Windows Meskauskas Audrius
2005-09-10 10:18       ` Mauve coding on Windows Martin Olsson
2005-09-10 14:49         ` Dalibor Topic
2005-09-10  6:47 ` David Gilbert
2005-09-10  8:58 ` Andrew Haley
2005-09-10 17:15   ` Meskauskas Audrius
2005-09-16 17:08     ` Tom Tromey
2005-09-16 18:12       ` Meskauskas Audrius
2005-09-10 10:28 Jeroen Frijters

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=4322A084.8010802@object-refinery.com \
    --to=david.gilbert@object-refinery.com \
    --cc=audriusa@bluewin.ch \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=mnemo@minimum.se \
    /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).