public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
	       "Dominique d'Humieres" <dominiq@lps.ens.fr>
Subject: Re: [committed, libjava] XFAIL sourcelocation (PR libgcj/55637) backported to 4.8.3
Date: Thu, 03 Apr 2014 15:31:00 -0000	[thread overview]
Message-ID: <983053F5-B803-4518-8BF1-30A2120E4F02@lps.ens.fr> (raw)
In-Reply-To: <yddwqf8nh2e.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>


Thanks for the tip. What should I do now? Should I fix the ChangeLog entry and add a new one or do nothing?

Dominique

Le 2 avr. 2014 à 12:47, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> a écrit :

> dominiq@lps.ens.fr (Dominique Dhumieres) writes:
> 
>> ro@CeBiTec.Uni-Bielefeld.DE (Rainer Orth) wrote:
>>> Sure, patch preapproved.
>> 
>> Commited as r208983:
>> 
>> 2014-04-01  Dominique d'Humieres <dominiq@lps.ens.fr>    
>>            Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
>> 
>>        PR libgcj/55637        
>>        * testsuite/libjava.lang/sourcelocation.xfail: New file.
> 
> Btw, the customary format for such a ChangeLog entry is
> 
> 2014-04-01  Dominique d'Humieres <dominiq@lps.ens.fr>    
> 
> 	Backport from mainline
> 	2014-02-20  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
> 
>        PR libgcj/55637
>        * testsuite/libjava.lang/sourcelocation.xfail: New file.
> 
> This way, you can easily see when the original went in.
> 
> 	Rainer
> 
> -- 
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2014-04-03 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 10:29 Dominique Dhumieres
2014-04-02 10:48 ` Rainer Orth
2014-04-03 15:31   ` Dominique d'Humières [this message]
2014-04-03 15:33     ` Rainer Orth
2014-04-04  7:08       ` Dominique Dhumieres

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=983053F5-B803-4518-8BF1-30A2120E4F02@lps.ens.fr \
    --to=dominiq@lps.ens.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).