From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ricardo Wurmus" <rekado@elephly.net>,
"Timothy Sample" <samplet@ngyro.com>,
"Ludovic Courtès" <ludo@gnu.org>,
62570-done@debbugs.gnu.org
Subject: bug#62570: [PATCH 3/6] gnu: texlive-latex-bigfoot: Replace with texlive-bigfoot.
Date: Tue, 18 Apr 2023 15:30:57 +0200 [thread overview]
Message-ID: <87y1mpjp0u.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87bkjyjzen.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 08 Apr 2023 15:07:12 +0200")
Hello,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> So, do we (not only the two of us, obviously) agree on the
> `simple-texlive-package' approach? If so, what should we do about
> "source"?
I applied the whole set. The question above is still open, but I'm
closing this particular report for now.
Thank you for your input.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-04-18 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 15:30 [bug#62570] [PATCH 0/6] Fix name and dependencies of a few Texlive packages Nicolas Goaziou
2023-03-31 15:32 ` [bug#62570] [PATCH 1/6] gnu: Add texlive-ncctools Nicolas Goaziou
2023-03-31 15:32 ` [bug#62570] [PATCH 2/6] gnu: Add texlive-relsize Nicolas Goaziou
2023-03-31 15:32 ` [bug#62570] [PATCH 3/6] gnu: texlive-latex-bigfoot: Replace with texlive-bigfoot Nicolas Goaziou
2023-04-07 16:48 ` Simon Tournier
2023-04-07 18:01 ` Nicolas Goaziou
2023-04-08 9:35 ` Simon Tournier
2023-04-08 13:07 ` Nicolas Goaziou
2023-04-18 13:30 ` Nicolas Goaziou [this message]
2023-03-31 15:32 ` [bug#62570] [PATCH 4/6] gnu: texlive-latex-acronym: Replace with texlive-acronym Nicolas Goaziou
2023-03-31 15:32 ` [bug#62570] [PATCH 5/6] gnu: texlive-latex-totcount: Replace with texlive-totcount Nicolas Goaziou
2023-03-31 15:32 ` [bug#62570] [PATCH 6/6] gnu: texlive-latex-lastpage: Replace with texlive-lastpage Nicolas Goaziou
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=87y1mpjp0u.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=62570-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
--cc=samplet@ngyro.com \
--cc=zimon.toutoune@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.