From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27550@debbugs.gnu.org
Subject: [bug#27550] [PATCH 0/2] cuirass: Prepare (guix git) integration.
Date: Wed, 05 Jul 2017 23:44:07 +0200 [thread overview]
Message-ID: <87fueasgns.fsf@gnu.org> (raw)
In-Reply-To: <864lurnxd6.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 05 Jul 2017 09:42:13 +0200")
Hello,
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
>> Looks nice!
>
> Thanks :)
>
>> Leftover ‘pk’. :-)
>
> Oops !
>
>>
>> Maybe s/store-dir/checkout/ for clarity.
>>
>> Please add a check for (guix git) in configure.ac.
>
> Ok.
>
>>
>> Now there are ‘git-error’ exception that can be thrown from there.
>> Should the ‘cuirass’ program catch them, report them on stderr, and keep
>> going? Maybe we can ignore that for now (throwing is better than
>> silently ignoring Git problems anyway.)
>
> Maybe we can ignore them for now, and when guile-git will support
> git-error integer error code -> string conversion, we can report them
> and keep going as you suggested ?
Sure, sounds good, let’s ignore this for now.
Thank you!
Ludo’.
next prev parent reply other threads:[~2017-07-05 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 15:00 [bug#27550] [PATCH 0/2] cuirass: Prepare (guix git) integration Mathieu Othacehe
2017-07-01 15:02 ` [bug#27550] [PATCH 1/2] repo: remove git-repo Mathieu Othacehe
2017-07-01 15:02 ` [bug#27550] [PATCH 2/2] utils: Remove useless procedures Mathieu Othacehe
2017-07-03 12:07 ` [bug#27550] [PATCH 0/2] cuirass: Prepare (guix git) integration Ludovic Courtès
2017-07-03 12:15 ` Mathieu Othacehe
2017-07-03 13:52 ` Mathieu Othacehe
2017-07-04 21:32 ` Ludovic Courtès
2017-07-05 7:42 ` Mathieu Othacehe
2017-07-05 11:54 ` Mathieu Othacehe
2017-07-05 21:45 ` Ludovic Courtès
2017-07-06 7:00 ` bug#27550: " Mathieu Othacehe
2017-07-05 21:44 ` Ludovic Courtès [this message]
2017-07-03 14:14 ` [bug#27550] " Ludovic Courtès
2017-07-03 14:28 ` Mathieu Othacehe
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=87fueasgns.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27550@debbugs.gnu.org \
--cc=m.othacehe@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 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).