all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Evgenii Lepikhin <e.lepikhin@corp.mail.ru>
Cc: 54644@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#54644] [PATCH 4/7] gnu: rust-minimal-lexical 0.2: Update to 0.2.1.
Date: Fri, 01 Apr 2022 17:32:25 +0200	[thread overview]
Message-ID: <c31ecf9e9c2aa08b44f0228dcc42a2d2105e8f0b.camel@telenet.be> (raw)
In-Reply-To: <87y20oj4il.fsf@corp.mail.ru>

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

Evgenii Lepikhin schreef op vr 01-04-2022 om 16:51 [+0300]:
> Could you advise on sending a new version of the patches, please?
> Should I create a completely new patchset with separate patches for
> each package individually or just one patch with all the fixes is
> enough now?

I would send a new patch series with a version number: [PATCH v2 0/7]
..., [PATCH v2 7/7] ..., to the same bug number 54644@debbugs.gnu.org.
You can use the -v2 option of "git send-email" for this.

If a single ‘fixup patch’ were used, then the commit history would be
messier and the reviewer would need to remember which ‘wrong’ things in
the earlier patches are fixed in the fixup patch.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-04-01 15:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 21:21 [bug#54644] [PATCH 1/7] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:33 ` [bug#54644] [PATCH 2/7] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 3/7] gnu: rust-located-yaml 0.2: Update to 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 4/7] gnu: rust-minimal-lexical " Evgenii Lepikhin via Guix-patches via
2022-03-31 11:59   ` Maxime Devos
2022-03-31 12:01   ` Maxime Devos
2022-03-31 14:47     ` Efraim Flashner
2022-03-31 15:40       ` Maxime Devos
2022-03-31 22:30         ` Evgenii Lepikhin via Guix-patches via
2022-04-01  6:38           ` Maxime Devos
2022-04-01 13:51             ` Evgenii Lepikhin via Guix-patches via
2022-04-01 15:32               ` Maxime Devos [this message]
2022-03-30 21:36 ` [bug#54644] [PATCH 5/7] gnu: rust-nom 7.1: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:37 ` [bug#54644] [PATCH 6/7] gnu: rust-serde-regex 1: Update to 1.1.0 Evgenii Lepikhin via Guix-patches via
2022-03-31 11:56   ` Maxime Devos
2022-03-31 19:16     ` Maxime Devos
2022-03-31 11:58   ` Maxime Devos
2022-03-31 14:48     ` Efraim Flashner
2022-03-30 21:37 ` [bug#54644] [PATCH 7/7] gnu: Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54   ` [bug#54644] [PATCH v2 2/6] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54   ` [bug#54644] [PATCH v2 3/6] gnu: rust-located-yaml: Add 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54   ` [bug#54644] [PATCH v2 4/6] gnu: rust-nom 7: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54   ` [bug#54644] [PATCH v2 5/6] gnu: rust-serde-regex: Add 1.1.0 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54   ` [bug#54644] [PATCH v2 6/6] Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-05-16 13:49   ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-05-30  8:18     ` bug#54644: " Efraim Flashner

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=c31ecf9e9c2aa08b44f0228dcc42a2d2105e8f0b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54644@debbugs.gnu.org \
    --cc=e.lepikhin@corp.mail.ru \
    --cc=efraim@flashner.co.il \
    /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.