From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 38678@debbugs.gnu.org
Subject: [bug#38678] Command line option in addition to GUIX_PACKAGE_PATH - Reason?
Date: Mon, 20 Jan 2020 17:21:26 +0100 [thread overview]
Message-ID: <CAJ3okZ1V0-jnDW7S9Ay6=pM0YG-s==-Pec1=Ffe4JSucGaEHNw@mail.gmail.com> (raw)
In-Reply-To: <87d0bhkm6l.fsf@ambrevar.xyz>
On Sat, 18 Jan 2020 at 13:01, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> > Why are you the author of ee9a735bc8 [1]?
>
> Good question :( My apologies, it seems that when I resolve the
> conflict your authorship was lost in the process. Sorry about that.
You owe me a beer at Guix Days 1. ;-)
> > Why there are lines modified in guix.texi 21f4fbdd84 [2] which are not
> > in the original patch [3]?
>
> Hmmm... Looks like Emacs' ws-buttler had a hickup here. I don't know
> why, sorry about that.
Well, you owe me a beer at Guix Days 2. ;-)
Yes, extra spaces had been introduced by these commits:
21531add320
83db0205060
The good point is now, it is fixed. ;-)
What I do not understand is: why 'ws-buttler' had a hiccup? Did you
modify my patch? I mean ws-buttler generally works by hooking
(before-save-hook), therefore to have a hiccup, 'ws-buttler' needed a
modification then a save, right? Why?
Thank you for reviewing and pushing.
I will remind that you owe me 2 belgian beers. ;-)
Cheers,
simon
next prev parent reply other threads:[~2020-01-20 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pnglj2ka.fsf@ambrevar.xyz>
[not found] ` <CAJ3okZ3X5DZ3DVDXY5_WHEOzL01=nJGkJeBHZxL-1eLS3x8c8g@mail.gmail.com>
[not found] ` <87sglgsiey.fsf@lassieur.org>
[not found] ` <878sn8inru.fsf@ambrevar.xyz>
[not found] ` <87o8w4mewg.fsf@gnu.org>
[not found] ` <87tv5wfdrm.fsf@ambrevar.xyz>
[not found] ` <CAJ3okZ0_5AB57FgNyagAA-KCOW=o7AgDrr4v5p8n4XvEmJH7=g@mail.gmail.com>
[not found] ` <87lfr8fd9u.fsf@ambrevar.xyz>
[not found] ` <20191226213108.753f8ab7@scratchpost.org>
[not found] ` <CAJ3okZ2HSh_WbiWEz65-A_LZLgN91Dc-rAQe_7PbA09YQid64Q@mail.gmail.com>
[not found] ` <87blr3eao0.fsf@ambrevar.xyz>
[not found] ` <CAJ3okZ3G5YteTpMJdsfUHHp=LrzZ593OrZAaupk=x7bp3CZ-3Q@mail.gmail.com>
[not found] ` <87ftge13h5.fsf@ambrevar.xyz>
2020-01-17 16:19 ` [bug#38678] Command line option in addition to GUIX_PACKAGE_PATH - Reason? zimoun
2020-01-17 16:56 ` Pierre Neidhardt
2020-01-17 18:14 ` zimoun
2020-01-17 18:38 ` Pierre Neidhardt
2020-01-18 12:01 ` Pierre Neidhardt
2020-01-18 12:09 ` Pierre Neidhardt
2020-01-20 16:21 ` zimoun [this message]
2020-01-20 18:12 ` Pierre Neidhardt
2020-01-20 18:35 ` zimoun
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='CAJ3okZ1V0-jnDW7S9Ay6=pM0YG-s==-Pec1=Ffe4JSucGaEHNw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=38678@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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).