public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pierre Vittet <piervit@pvittet.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, MELT] fix useless forcing of GCC garbage collector
Date: Mon, 09 May 2011 21:56:00 -0000	[thread overview]
Message-ID: <4DC83053.5020207@pvittet.com> (raw)
In-Reply-To: <20110509190354.ec3141cc.basile@starynkevitch.net>

Thanks you for the correction, I will take care next time.

Pierre
On 09/05/2011 19:03, Basile Starynkevitch wrote:
> On Mon, 09 May 2011 14:15:30 +0200
> Pierre Vittet<piervit@pvittet.com>  wrote:
>
>    
>> This patch is for the MELT branch.
>>      
> The diff file was slightly wrong (diff run under gcc/). Pierre, you
> should run svn diff -x -p at the top source directory to get a patch
> file.
>
> I applied the patch. The gcc/ChangeLog.MELT proposed by Pierre was
> wrong, I wrote:
>
> 2011-05-09  Pierre Vittet<piervit@pvittet.com>
>
> 	* melt-runtime.c (melt_garbcoll): Don't force collection by
> 	gcc_collect.
>
> Committed revision 173576.
>
>
> Folks, what is the procedure to get Pierre an svn+ssh write access to
> GCC svn server (mostly for the MELT branch, and write after approval
> for the rest). As far as I understood, all legal stuff has been
> completed.
>
>    
>> My GCC contributor number is 634276.
>>      
> This is the copyright assignment legal document reference for Pierre Vittet.
>
> What does he (or me) have to do to get svn+ssh://gcc.melt.org/ write access?
>
> Cheers.
>    

      parent reply	other threads:[~2011-05-09 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 16:25 Pierre Vittet
2011-05-09 17:54 ` Basile Starynkevitch
2011-05-09 17:59   ` Basile Starynkevitch
2011-05-09 21:56   ` Pierre Vittet [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=4DC83053.5020207@pvittet.com \
    --to=piervit@pvittet.com \
    --cc=gcc-patches@gcc.gnu.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).