all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Leo Famulari <leo@famulari.name>,
	Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 39228@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#39228] [PATCH] gnu: Add libvnc.
Date: Wed, 22 Jan 2020 18:43:26 +0100	[thread overview]
Message-ID: <53cbb7b4-945a-48c7-2451-00913f36ccca@web.de> (raw)
In-Reply-To: <20200122173302.GA13752@jasmine.lan>



On 22.01.20 18:33, Leo Famulari wrote:
> On Wed, Jan 22, 2020 at 01:21:59PM +0100, Hartmut Goebel wrote:
>> Am 22.01.20 um 13:17 schrieb Jonathan Brielmaier:
>>> gnu: Rename module gnutls to tls.
>>>
>>> should be
>>>
>>> gnu: Rename module tigervnc to vnc.
>>
>> ARGL! I should not do this kind of work when traveling.
>>
>> @efraim: Any chance to clean this up?
>
> We don't rewrite the commits after they are pushed to Savannah's master
> branch. So, it's important to be careful when pushing, but please "don't
> beat yourself up" over this :)
>

As well as the body of the commit message is correct:

* gnu/packages/tigervnc.scm: Rename to...
* gnu/packages/vnc.scm: ... this.  Change module name accordingly. Sort
   used modules.
* gnu-system.am (GNU_SYSTEM_MODULES): Rename tigervnc module to vnc.

      reply	other threads:[~2020-01-22 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 21:10 [bug#39228] [PATCH] gnu: Add libvnc Hartmut Goebel
2020-01-21 21:52 ` [bug#39228] [Patch v2] " Hartmut Goebel
2020-01-21 21:57 ` [bug#39228] [PATCH] " Leo Famulari
2020-01-22  8:47   ` Hartmut Goebel
2020-01-22  9:16     ` Efraim Flashner
2020-01-22 12:09       ` bug#39228: " Hartmut Goebel
2020-01-22 12:17         ` [bug#39228] " Jonathan Brielmaier
2020-01-22 12:21           ` Hartmut Goebel
2020-01-22 17:33             ` Leo Famulari
2020-01-22 17:43               ` Jonathan Brielmaier [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=53cbb7b4-945a-48c7-2451-00913f36ccca@web.de \
    --to=jonathan.brielmaier@web.de \
    --cc=39228@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=h.goebel@crazy-compilers.com \
    --cc=leo@famulari.name \
    /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.