From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 40064@debbugs.gnu.org
Subject: [bug#40064] Resubmission of patch for Package Description for CRAN Package r-crochet
Date: Sat, 14 Mar 2020 23:41:20 +0100 [thread overview]
Message-ID: <87tv2qlfu7.fsf@nckx> (raw)
In-Reply-To: <54793c0b-ca82-e80c-1da6-b06ea709b091@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Hullo Naga,
Naga Malleswari 写道：
> I am resubmitting with the new patch file for CRAN Package
> Description
> r-crochet.
Thank you!
> Hope it's the correct way which i was following.
Sending a patch to guix-patches@gnu.org will always create a new
bug number[0]. In this case, you don't want that to happen.
The way to submit a revised patch is to send it to the previous
bug number (nnnnn@debbugs.gnu.org, in this case
40040@debbugs.gnu.org) and clearly mark it as a new revision (V2,
V3, &c.).
If, like me, you use git send-email, this is easy:
~/guix $ git send-email --to=40040@debbugs.gnu.org -v2 -1
I've merged the two duplicate bug numbers for this package.
Kind regards,
T G-R
[0]:
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches;include=subject%3Ar-crochet
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-03-14 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 18:16 [bug#40064] Resubmission of patch for Package Description for CRAN Package r-crochet Naga Malleswari
2020-03-14 22:41 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-03-15 12:33 ` Naga Malli CH
2020-03-17 9:50 ` [bug#40040] " Danny Milosavljevic
2020-03-19 8:13 ` Naga Malleswari
2020-03-19 11:38 ` Danny Milosavljevic
2020-03-19 17:35 ` Naga Malleswari
2020-03-19 17:53 ` Danny Milosavljevic
2020-03-19 18:01 ` Naga Malleswari
2020-03-20 17:40 ` Naga Malleswari
2020-03-21 13:18 ` bug#40040: " Danny Milosavljevic
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=87tv2qlfu7.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=40064@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).