public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Casey Marshall <csm@gnu.org>
To: Daniel Kegel <dkegel@google.com>
Cc: " Steve McKay☄ " <smckay@google.com>,
	"Anthony Green" <green@redhat.com>,
	mauve-discuss@sources.redhat.com
Subject: Re: Patches for running mauve against wine + win32 vm
Date: Fri, 07 Sep 2007 05:16:00 -0000	[thread overview]
Message-ID: <AB280903-10B1-4860-83E4-E89A5AD190C8@gnu.org> (raw)
In-Reply-To: <545d88bc0709061438k6859611ai4e68cb7591a5910f@mail.gmail.com>

On Sep 6, 2007, at 2:38 PM, Daniel Kegel wrote:

> On 9/6/07, Steve McKay☄ <smckay@google.com> wrote:
>>> I've got more fixes in the pipeline, but I'd like to get my previous
>>> patch cleared out if possible. Do you have any questions/need any
>>> changes, or can the patch be applied?
>> This is taking quite a bit longer than I expected. Am I going about
>> things the right way? Is there anything I can do to expedite the
>> process?
>
> Patience, grasshopper.  I'd say the thing to do is simply
> post all your patches, and make sure to explain why each
> one is needed.  It might also be a good idea to have a little
> web page somewhere explaining what you are doing
> that also links to all your patches.
>

As a left-field idea, since I think most people formerly involved  
with Mauve have their attention elsewhere, it might just be fine to  
get Steve CVS write access to Mauve. The contribution policy for  
Mauve is AFAIK liberal enough (probably something like "put your  
copyright notice on stuff you contribute, and please make it GPL")  
that it might be fine for you to just check this stuff in.

I think the request form is still: http://sources.redhat.com/cgi-bin/ 
pdw/ps_form.cgi

(note, I'm not recognized as someone who can approve CVS requests for  
sourceware.org, I'm just commenting from the peanut gallery)

  reply	other threads:[~2007-09-07  5:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f2ee4520708031409o723d606bx78689a245f9fb5ef@mail.gmail.com>
2007-08-27 20:01 ` Fwd: " Steve McKay☄
2007-08-28  0:40   ` Daniel Kegel
     [not found]     ` <46D42F38.8030100@redhat.com>
2007-08-28 15:10       ` Daniel Kegel
2007-08-28 18:04       ` Steve McKay☄
2007-08-31 17:33         ` Steve McKay☄
2007-09-06 21:07           ` Steve McKay☄
2007-09-06 21:39             ` Daniel Kegel
2007-09-07  5:16               ` Casey Marshall [this message]
2007-09-07 22:50                 ` Steve McKay☄
     [not found]                   ` <46E1DCB1.8090405@redhat.com>
2007-09-12 22:32                     ` Steve McKay☄

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=AB280903-10B1-4860-83E4-E89A5AD190C8@gnu.org \
    --to=csm@gnu.org \
    --cc=dkegel@google.com \
    --cc=green@redhat.com \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=smckay@google.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).