From: Marius Bakke <mbakke@fastmail.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add kakoune
Date: Fri, 27 Jan 2017 01:47:04 +0100 [thread overview]
Message-ID: <87inp12ut3.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87poj9z85l.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Carlo Zancanaro <carlo@zancanaro.id.au> writes:
> On Thu, Jan 26 2017, Marius Bakke wrote
>> Would you like to fix it? Good catch, sorry for making the mistake on
>> your behalf!
>
> No worries!
>
> I've attached a patch to move it to a snippet. I wasn't sure how to word
> the commit message (this is the first time I've updated a package), so I
> hope it's okay. If not, feel free to change it.
Thank you! I tweaked it to match the convention of mentioning which
fields changed.
> Thanks for the comments regarding patches/snippets/phases. I think I'll
> just need to hang around a bit longer and see how things are done to get
> a feel for it myself.
To clarify, snippets and patches change the source presented to the
user with `guix build -S`. Substitutions that works around build or
paradigm problems are better fit in a phase.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-27 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 3:43 [PATCH] gnu: Add kakoune Carlo Zancanaro
2016-12-30 4:44 ` Carlo Zancanaro
2016-12-30 19:25 ` Leo Famulari
2016-12-30 23:19 ` Carlo Zancanaro
2017-01-10 22:26 ` Leo Famulari
2017-01-21 1:49 ` Carlo Zancanaro
2017-01-26 10:20 ` Ludovic Courtès
2017-01-26 12:26 ` Carlo Zancanaro
2017-01-26 20:19 ` Marius Bakke
2017-01-26 21:43 ` Carlo Zancanaro
2017-01-26 22:09 ` Marius Bakke
2017-01-26 23:57 ` Carlo Zancanaro
2017-01-27 0:47 ` Marius Bakke [this message]
2017-01-27 23:00 ` gzip embedded timestamps 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
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=87inp12ut3.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@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 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).