Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] New Year procedure - done
Date: Mon, 01 Jan 2007 06:15:00 -0000	[thread overview]
Message-ID: <E1H1GRW-0000mf-B0@fencepost.gnu.org> (raw)
In-Reply-To: <20070101060212.GG3428@adacore.com> (message from Joel Brobecker 	on Mon, 1 Jan 2007 10:02:12 +0400)

> Date: Mon, 1 Jan 2007 10:02:12 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Now that it's 2007 and that we've already had our first change
> (the lucky number 1 was Mark K :-), I have rotated the ChangeLog
> and updated the copyright year in top.c.
> 
> 2007-01-01  Joel Brobecker  <brobecker@adacore.com>
> 
>         Followed the Start of New Year Procedure:
>         * ChangeLog-2006: New file, containing all the entries for 2006.

This new file requires a new line in gdb/config/djgpp/fnchange.lst.


  reply	other threads:[~2007-01-01  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01  6:01 Joel Brobecker
2007-01-01  6:15 ` Eli Zaretskii [this message]
2007-01-01  7:03   ` Joel Brobecker
2007-01-01  7:16     ` Eli Zaretskii

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=E1H1GRW-0000mf-B0@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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