From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 52966@debbugs.gnu.org
Subject: [bug#52966] [PATCH 1/6] gnu: Add python-piexif.
Date: Sat, 08 Jan 2022 23:02:53 +0100 [thread overview]
Message-ID: <878rvp3mya.fsf@gnu.org> (raw)
In-Reply-To: <05cc89ec4c7cb0eda6945690544469f519811ecf.1641160577.git.h.goebel@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 2 Jan 2022 22:59:37 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> + (description "@code{Piexif} simplifies interacting with EXIF data in
> +Python. It includes the tools necessary for extracting, creating,
> +manipulating, converting and writing EXIF data to JPEG, WebP and TIFF files.")
> + (license license:expat)))
[...]
> + (description "@code{Nikola} generated static websites and blogs. Out of the
> +box, it supports reStructuredText, Markdown, IPython (Jupyter) Notebooks and
> +HTML, and has plugins for many other formats.")
> + (license license:expat)))
BTW, there’s no reason to use @code for proper nouns; you can probably
just remove it in these two cases (@code is used for code snippets,
rendered using a fixed-width font.)
Ludo’.
prev parent reply other threads:[~2022-01-08 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 21:59 [bug#52966] [PATCH 1/6] gnu: Add python-piexif Hartmut Goebel
2022-01-02 22:00 ` [bug#52966] [PATCH 2/6] gnu: Add python-pyrss2gen Hartmut Goebel
2022-01-02 22:00 ` [bug#52966] [PATCH 3/6] gnu: Add python-yapsy Hartmut Goebel
2022-01-02 22:00 ` [bug#52966] [PATCH 4/6] gnu: Add python-doit Hartmut Goebel
2022-01-02 22:00 ` [bug#52966] [PATCH 5/6] gnu: Add python-phpserialize Hartmut Goebel
2022-01-02 22:00 ` [bug#52966] [PATCH 6/6] gnu: Add nikola Hartmut Goebel
2022-01-08 22:01 ` [bug#52966] [PATCH 1/6] gnu: Add python-piexif Ludovic Courtès
2022-01-15 20:37 ` bug#52966: " Hartmut Goebel
2022-01-08 22:02 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rvp3mya.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52966@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).