From: Joseph Myers <joseph@codesourcery.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Rafal Luzynski <digitalfreak@lingonborough.com>,
<libc-alpha@sourceware.org>,
Thomas Schwinge <thomas@schwinge.name>
Subject: Re: [hurd,commited] hurd: Add missing fcntl-internal.h
Date: Mon, 29 Jan 2018 21:32:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801291638580.11517@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180129141634.ltw66472sha5ce7y@var.youpi.perso.aquilenet.fr>
On Mon, 29 Jan 2018, Samuel Thibault wrote:
> > > +2008-12-18 Thomas Schwinge <tschwinge@gnu.org>
> >
> > Is this really 2008 or a typo?
>
> That fcntl-internal.h code is really from 2008. Just nobody had taken
> the time to upstream it so far.
ChangeLog dates should be commit dates rather than possibly older dates
when a patch was written, according to the GNU Coding Standards.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2018-01-29 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 18:15 Samuel Thibault
2018-01-29 15:30 ` Rafal Luzynski
2018-01-29 16:34 ` Samuel Thibault
2018-01-29 21:32 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1801291638580.11517@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=thomas@schwinge.name \
/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).