public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
	libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v2 3/6] Implement the %OB specifier - alternative month names (bug 10871)
Date: Thu, 02 Jun 2016 07:03:00 -0000	[thread overview]
Message-ID: <574FDA37.2000704@cs.ucla.edu> (raw)
In-Reply-To: <480412909.686000.92369107-bdae-4a8b-b71f-99b919bc0cf0.open-xchange@poczta.nazwa.pl>

Rafal Luzynski wrote:
> Sounds nice, I will
> have to read more about it. (Any hints, links etc. are welcome.)

Alas, I don't know of any documentation for that, you can look in the source 
code tho. (I'm by no means an expert in this stuff, alas.)

> What if a programmer, for example an author of cal(1), just rebuilds
> the unmodified source while it should be modified? Is there a way to
> tell them they should at least verify their source code?

Not really. I wouldn't worry much about that problem, to be honest.

  reply	other threads:[~2016-06-02  7:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25  0:55 Rafal Luzynski
2016-03-29  9:02 ` Florian Weimer
2016-03-29 10:59   ` keld
2016-11-04 13:36   ` Florian Weimer
2016-11-05 10:42     ` Rafal Luzynski
2016-03-29 14:15 ` Carlos O'Donell
2016-03-29 23:23   ` Rafal Luzynski
2016-03-29 14:31 ` Dmitry V. Levin
2016-03-29 23:31   ` Rafal Luzynski
2016-06-01 10:42     ` Dmitry V. Levin
2016-06-01 21:51       ` Rafal Luzynski
2016-06-01 22:20         ` Paul Eggert
2016-06-01 23:54           ` Rafal Luzynski
2016-06-02  7:03             ` Paul Eggert [this message]
2016-06-03  7:08               ` Rafal Luzynski

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=574FDA37.2000704@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=digitalfreak@lingonborough.com \
    --cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).