From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24011] Fixed small type in comment for locale bs_BA
Date: Mon, 31 Dec 2018 18:34:00 -0000 [thread overview]
Message-ID: <bug-24011-716-GaONFEgPzg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24011-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24011
Rafal Luzynski <digitalfreak at lingonborough dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |digitalfreak@lingonborough.
| |com
--- Comment #1 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
This patch is trivial so I am in favor of pushing it now.
1. Should I use "Pander" as your real name, as the author of the patch? People
usually put their real first and last names but I don't mind if you choose to
this it in case of this patch. Or, do you maybe prefer that someone else
claims the authorship of the patch?
2. Could you maybe generate the complete patch using "git format-patch" and
post it to libc-alpha@sourceware.org instead, so that it contains "Subject:"
and "From:" and "Date:" fields? For locale data and for trivial patches the
copyright assignment is not required.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-12-31 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 7:53 [Bug localedata/24011] New: " pander at users dot sourceforge.net
2018-12-31 18:34 ` digitalfreak at lingonborough dot com [this message]
2019-01-01 13:27 ` [Bug localedata/24011] " pander at users dot sourceforge.net
2019-01-02 22:52 ` cvs-commit at gcc dot gnu.org
2019-01-02 22:57 ` digitalfreak at lingonborough dot com
2019-01-24 20:27 ` jsm28 at gcc dot gnu.org
2019-01-31 17:19 ` cvs-commit at gcc dot gnu.org
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=bug-24011-716-GaONFEgPzg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).