Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ChangeLog entry dates...
Date: Tue, 27 Feb 2007 23:19:00 -0000	[thread overview]
Message-ID: <17892.48254.243673.405650@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070227230716.GQ13153@adacore.com>

 > I have a question/suggestion regarding the date that should be used in
 > a ChangeLog entry, like so:
 > 
 >     2007-02-27  Joel Brobecker  <brobecker@adacore.com>
 > 
 > I suggest we try to use the UTC date at the time the change was
 > checked in.
 > 
 > With contributors such as Nick that leave at UTC+something in
 > New Zealand (according to email address), and folks like myself
 > that leave on the West Coast of North America, which is UTC-lots,
 > it's very easy to have entries that is one day ahead of me, thus
 > breaking the date ordering...

I think something like below works, at least for Emacs users (this is what
Emacs uses now).  Yes, I know GDB isn't Emacs -- but it would stop people
like me being a problem, and mean I don't have to set my clock to UTC
(or set add-log-time-zone-rule to t in my .emacs).

-- 
Nick                                           http://www.inet.net.nz/~nickrob


*** ChangeLog	28 Feb 2007 10:58:39 +1300	1.8201
--- ChangeLog	28 Feb 2007 12:13:44 +1300	
*************** mode: change-log
*** 1455,1458 ****
--- 1455,1459 ----
  left-margin: 8
  fill-column: 74
  version-control: never
+ add-log-time-zone-rule: t
  End:


  reply	other threads:[~2007-02-27 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 23:07 Joel Brobecker
2007-02-27 23:19 ` Nick Roberts [this message]
2007-02-28  1:02   ` Daniel Jacobowitz
2007-02-28  1:21     ` Nick Roberts

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=17892.48254.243673.405650@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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