public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Zander <zander@javalobby.org>
To: mauve-discuss@sources.redhat.com
Subject: Re: Mauve patches.
Date: Sat, 17 Apr 2004 14:45:00 -0000	[thread overview]
Message-ID: <200404171644.21352.zander@javalobby.org> (raw)
In-Reply-To: <1082069767.1986.76.camel@elsschot.wildebeest.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 16 April 2004 00:56, you wrote:
> > > > > I hope you'll agree that its more important to have people
> > > > > creating patches and moving the project forward then to always
> > > > > have a 100% correct CVS. (problems can be fixed post-commit)
> > > >
> > > > No!
> > >
> > > would you care to elaborate on your position?
> >
> > Sure: "Problems should be fixed pre-commit."
>
> I agree. Mauve is actually used daily by people (me). And some people
> even use it in autobuilders/testers which are updated from CVS.

Hmm, I should have been more clear then. I naturally always will keep 
things compiling (one of the fixes I had was to get it compiling with suns 
Javac, for example).
I would never change the content of a class significantly without prior 
consent on the list.

The problems I 'expect' will be formatting things and other little things 
that I miss due to my different background. I put the "expect" between 
quotes because its not like I feel these things will happen; its just a 
saveguard for the rest of the team that if I commit something thats not up 
to spec; feel free to change it.

So I repeat my request for a cvs account..

Cheers!
- -- 
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAgULBCojCW6H2z/QRAiAXAJ9b232cutzP1a24L1iSRgn34I6pJQCffqAd
UMwMzP7qKpews57QPh0jN/4=
=Hd8X
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-04-17 14:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  7:55 Thomas
2004-04-06  8:47 ` Michael Koch
2004-04-08 19:34   ` Thomas Zander
2004-04-08 19:50     ` Michael Koch
2004-04-08 19:58       ` Andrew Haley
2004-04-11  6:48         ` Thomas Zander
2004-04-11 12:22           ` David Lichteblau
2004-04-11 17:20             ` Thomas Zander
2004-04-11 18:57               ` David Lichteblau
2004-04-11 19:37                 ` Thomas Zander
2004-04-12  4:12                   ` C. Brian Jones
2004-04-16 20:23                     ` Anthony Green
2004-04-16 22:57                       ` C. Brian Jones
2004-04-13 13:22                 ` Andrew Haley
2004-04-13 13:55                   ` Thomas
2004-04-13 14:30                     ` Andrew Haley
2004-04-13 17:14                       ` Thomas Zander
2004-04-13 17:45                         ` Andrew Haley
2004-04-13 18:59                           ` Thomas Zander
2004-04-14  9:56                             ` Andrew Haley
2004-04-14  0:09                     ` Bill McFadden
2004-04-15 22:56                 ` Mark Wielaard
2004-04-17 14:45                   ` Thomas Zander [this message]
2004-04-11 15:56           ` Archie Cobbs
2004-04-15 21:10           ` Mark Wielaard

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=200404171644.21352.zander@javalobby.org \
    --to=zander@javalobby.org \
    --cc=mauve-discuss@sources.redhat.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).