public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Nicolas BENOIT <nbenoit@tuxfamily.org>
Cc: gcc-patches@gcc.gnu.org, nicolas.benoit@cea.fr
Subject: Re: PING: [PATCH gcc/ebitmap] fix for ebitmap_clear_bit()
Date: Mon, 28 Sep 2009 16:24:00 -0000	[thread overview]
Message-ID: <mcrocovqcy4.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <4ABF56ED.9080805@tuxfamily.org> (Nicolas BENOIT's message of "Sun\, 27 Sep 2009 14\:13\:33 +0200")

Nicolas BENOIT <nbenoit@tuxfamily.org> writes:

> Here is a proposition for the ChangeLog entry :
>
> 2009-09-22  Nicolas Benoit  <nbenoit@tuxfamily.org>
>
> 	* ebitmap.c (ebitmap_clear_bit): Fixed map->cacheindex test and
> 	map>cache update when bit clearing results to an empty element.
>
>
> I don't know wether the date should correspond to the patch proposal
> or to the commit date, I let you update it if needed.

It should correspond to the commit date.  Whoever commits the patch
will normally correct that date.

Looking for volunteers to commit Nicolas's patches....

Ian

  reply	other threads:[~2009-09-28 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 17:12 Nicolas BENOIT
2009-09-22 17:45 ` Nicolas BENOIT
2009-09-26 23:36   ` Ian Lance Taylor
2009-09-27 12:21     ` Nicolas BENOIT
2009-09-28 16:24       ` Ian Lance Taylor [this message]
2009-10-12 17:20         ` Nicolas BENOIT
2009-10-29 18:00           ` Nicolas BENOIT
2010-02-24 19:00             ` Nicolas BENOIT
2010-02-24 20:49               ` Diego Novillo
2010-02-24 20:57                 ` Mark Mitchell
2010-02-26  2:34                   ` Diego Novillo
2010-02-25 18:21                 ` Nicolas BENOIT

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=mcrocovqcy4.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nbenoit@tuxfamily.org \
    --cc=nicolas.benoit@cea.fr \
    /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).