From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29135-done@debbugs.gnu.org
Subject: [bug#29135] awesome: Update to 4.2
Date: Tue, 7 Nov 2017 17:01:39 +0000 [thread overview]
Message-ID: <20171107170139.s43ada5yy6f67w3z@abyayala> (raw)
In-Reply-To: <87efpa59h4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Ludovic Courtès transcribed 0.7K bytes:
> ng0 <ng0@infotropique.org> skribis:
>
> > This updates awesome to 4.2.
> >
> > Someone using awesome should test if this fixes the runtime
> > errors 4.0 currently gives on GuixSD. In any case we can't
> > break it anymore than it is right now, so 4.2 fixes 150
> > issues as upstream states…
>
> Indeed.
>
> > In my opinion we should upstream the reproducibility fixes
> > we include locally, to share them with other projects.
>
> I agree. Are you volunteering? :-)
Too little time, too much conversation, different politics
and public outreach for just one person.
I'm doing this already, but it's harder to do for patches I
didn't write and can not argue for if they are questioned.
In my opinion we need a list of these patches, and it has
upstreaming can not rely on one person only.
> > From d4950d35c76145defbfaa77c814d08c243d1f7f4 Mon Sep 17 00:00:00 2001
> > From: ng0 <ng0@infotropique.org>
> > Date: Fri, 3 Nov 2017 15:07:58 +0000
> > Subject: [PATCH] gnu: awesome: Update to 4.2.
> >
> > * gnu/packages/wm.scm (awesome): Update to 4.2.
>
> Applied, thanks!
>
> Ludo'.
>
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.ng0.infotropique.org/dist/keys/
WWW: https://ng0.infotropique.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-07 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 15:12 [bug#29135] awesome: Update to 4.2 ng0
2017-11-07 16:39 ` bug#29135: " Ludovic Courtès
2017-11-07 17:01 ` ng0 [this message]
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=20171107170139.s43ada5yy6f67w3z@abyayala \
--to=ng0@infotropique.org \
--cc=29135-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.