public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mrs@wrs.com (Mike Stump)
To: wilson@cygnus.com
Cc: egcs@cygnus.com, law@cygnus.com
Subject: Re: Changelog time format
Date: Tue, 19 May 1998 15:59:00 -0000	[thread overview]
Message-ID: <199805191805.LAA04601@kankakee.wrs.com> (raw)

> To: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
> Date: Mon, 18 May 1998 12:44:42 -0700
> From: Jim Wilson <wilson@cygnus.com>

> If you want to argue the issue, then argue it with the FSF.  EGCS should
> just be following the FSF style guidelines, not creating our own.

Then we should put in the below patch.


Doing diffs in gcc/cp/ChangeLog.~1~:
*** gcc/cp/ChangeLog.~1~	Tue May 19 10:56:26 1998
--- gcc/cp/ChangeLog	Tue May 19 11:03:21 1998
*************** Wed Oct 11 16:30:34 1995  Brendan Kehoe 
*** 9578,9587 ****
  
  	* parse.y (fn.def1): Call split_specs_attrs in
  	declmods notype_declarator case.
- \f
- Use a consistent time stamp format in ChangeLog entries.
- Not everyone has Emacs 20 yet, so stick with Emacs 19 format for now.
- 
- Local Variables:
- add-log-time-format: current-time-string
- End:
--- 9578,9580 ----
--------------

             reply	other threads:[~1998-05-19 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-19 15:59 Mike Stump [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-05-09  6:51 Martin von Loewis
1998-05-09 23:32 ` Jeffrey A Law
1998-05-10  2:05   ` Martin von Loewis
1998-05-17 17:58 ` Jim Wilson
1998-05-17 22:03   ` Jeffrey A Law
1998-05-18  6:02     ` Franz Sirl
1998-05-18  6:02   ` Andreas Schwab
1998-05-18 15:38     ` Jim Wilson
1998-05-18 15:38       ` Martin von Loewis
     [not found]     ` <199805181944.MAA05755.cygnus.egcs@rtl.cygnus.com>
1998-05-18 23:58       ` Ulrich Drepper
1998-05-20  1:45         ` Jim Wilson
1998-05-20  2:27           ` Ulrich Drepper
1998-05-20 19:03             ` Jim Wilson
1998-05-20 19:03               ` Ulrich Drepper
1998-05-20  9:26           ` Dave Love

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=199805191805.LAA04601@kankakee.wrs.com \
    --to=mrs@wrs.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=wilson@cygnus.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).