public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Thomas Zander <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: patch committal.
Date: Tue, 04 May 2004 10:27:00 -0000	[thread overview]
Message-ID: <16535.28621.499614.841380@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <200405021704.12662.zander@javalobby.org>

Thomas Zander writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > On Sunday 02 May 2004 14:49, Andrew Haley wrote:
 > > Thomas Zander writes:
 > >  > I've requested a cvs account several times; but have not even
 > >  > received the courtesy of a yes/no answer.
 > >
 > > We should get you a CVS account.  However, your opinion that "its more
 > > important to have people creating patches and moving the project
 > > forward then to always have a 100% correct CVS" makes people worried.
 > 
 > That statement was discussed and I learned that mauve does not have
 > any sort of release cycle in which bugs can be fixed. Its
 > 'released' as a final product in CVS on a daily basis, so to say.
 > I agree that that takes a slightly different approach.

Cool.

 > > You should get CVS access, I think, 
 > That would be nice; anyone I can contact?

Tromey should be listening, and AFAICR he holds the keys.  Tom, you
there?

 > > but of course you'll still need to 
 > > post patches here for pre-commit discussion.  Everybody does that.
 > No problem, if you think that helps :-)

Oh yes.

Andrew.

      parent reply	other threads:[~2004-05-04 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 12:17 Thomas Zander
2004-05-02 12:50 ` Andrew Haley
2004-05-02 15:05   ` Thomas Zander
2004-05-02 23:49     ` C. Brian Jones
2004-05-04 10:27     ` Andrew Haley [this message]

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=16535.28621.499614.841380@cuddles.cambridge.redhat.com \
    --to=aph@redhat.com \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=zander@javalobby.org \
    /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).