unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Covrig <aarcov@gmail.com>
To: 73339@debbugs.gnu.org
Subject: [bug#73339] Incorrect multipart submission
Date: Mon, 23 Sep 2024 18:36:29 -0400	[thread overview]
Message-ID: <20240923183255.6292d3d4@mobile-dev> (raw)
In-Reply-To: <20240918211510.468854-1-aaron.covrig.us@ieee.org>

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

It would seem I did not do the multipart commit correctly, this issue
is the part 1/2
for https://issues.guix.gnu.org/73338; hopefully this one for pypandoc gets pickedup first by the build system.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2024-09-24  0:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 21:14 [bug#73339] [PATCH 1/2] gnu: pypandoc: Update to 1.13 and fix dependencies Aaron Covrig via Guix-patches via
2024-09-18 21:14 ` [bug#73338] [PATCH 2/2] gnu: impressive: Update to 13.2 and fix build Aaron Covrig via Guix-patches via
2024-09-23 22:38   ` [bug#73338] multipart patch split across issues Aaron Covrig
2024-10-24 21:21   ` [bug#73338] [PATCH] gnu: impressive: Update to 13.2 and fix build Aaron Covrig via Guix-patches via
2024-10-24 21:28   ` [bug#73338] merge 73338 73339 Aaron Covrig via Guix-patches via
2024-09-23 22:36 ` Aaron Covrig [this message]
2024-10-24 21:16 ` [bug#73339] [PATCH] gnu: pypandoc: Update to 1.14 Aaron Covrig via Guix-patches via
2024-10-24 23:33 ` [bug#73339] [PATCH v3 1/2] " Aaron Covrig via Guix-patches via
2024-10-24 23:33   ` [bug#73339] [PATCH v3 2/2] gnu: impressive: Update to 13.2 and fix build Aaron Covrig via Guix-patches via
2024-11-17 22:06   ` bug#73339: [PATCH v3 1/2] gnu: pypandoc: Update to 1.14 Ludovic Courtès

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=20240923183255.6292d3d4@mobile-dev \
    --to=aarcov@gmail.com \
    --cc=73339@debbugs.gnu.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. 
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).