From: Martin Becze <mjbecze@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37525-done@debbugs.gnu.org
Subject: [bug#37525] [PATCH v2 1/3] added recusive import functionality to the crate importer
Date: Tue, 01 Oct 2019 14:52:47 -0700 [thread overview]
Message-ID: <844562e2d2fba3cc2f5b0c563635777d@riseup.net> (raw)
In-Reply-To: <87r23wjgmk.fsf@gnu.org>
On 2019-10-01 21:33, Ludovic Courtès wrote:
> Hi,
>
> Applied!
>
> Note that I merged patches #2 and #3, because we usually document
> features as we add them, not separately. I had to fix up the Texinfo
> markup so that ‘--recursive’ is described under ‘crate’.
>
> Anyway it seems to work well, thanks for the patches!
>
> Ludo’.
Awesome thanks!
> features as we add them, not separately.
Do you mean in the same commit that makes the changes to the code? or
when you apply patches to master?
next prev parent reply other threads:[~2019-10-01 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 18:28 [bug#37525] [PATCH 0/3] Recursive option for crate importer Martin Becze
2019-09-26 18:31 ` [bug#37525] [PATCH 1/3] added recusive import functionality to the " Martin Becze
2019-09-26 18:31 ` [bug#37525] [PATCH 2/3] updated the crate import script to accept recursive option Martin Becze
2019-09-26 18:31 ` [bug#37525] [PATCH 3/3] updated docs for import crate Martin Becze
2019-10-01 20:17 ` [bug#37525] previous patch had mistake in docs Martin Becze
2019-10-01 20:54 ` [bug#37525] [PATCH v2 1/3] added recusive import functionality to the crate importer Martin Becze
2019-10-01 20:54 ` [bug#37525] [PATCH v2 2/3] updated the crate import script to accept recursive option Martin Becze
2019-10-01 20:54 ` [bug#37525] [PATCH v2 3/3] updated docs for import crate Martin Becze
2019-10-01 21:33 ` bug#37525: [PATCH v2 1/3] added recusive import functionality to the crate importer Ludovic Courtès
2019-10-01 21:52 ` Martin Becze [this message]
2019-10-02 14:28 ` [bug#37525] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=844562e2d2fba3cc2f5b0c563635777d@riseup.net \
--to=mjbecze@riseup.net \
--cc=37525-done@debbugs.gnu.org \
--cc=ludo@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 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.