all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Yoshinori Arai <kumagusu08@gmail.com>
Cc: 34283@debbugs.gnu.org
Subject: [bug#34283] [PATCH]Add: mypaint
Date: Tue, 5 Feb 2019 12:42:55 +0100	[thread overview]
Message-ID: <20190205124255.75e9f343@alma-ubu> (raw)
In-Reply-To: <20190202044421.44toqidrwk2f6acn@WaraToNora>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

Hi,

On Sat, 2 Feb 2019 13:44:21 +0900
Yoshinori Arai <kumagusu08@gmail.com> wrote:

> Hello,
> 
> I made mypaint package from git version.
> libmypaint-git, mypaint-brushes-git may be conflict with gimp package.
> 
> >From c9d5b440a6affccd0852e8686482b64aaef06bea Mon Sep 17 00:00:00
> >2001  
> From: Yoshinori Arai <kumagusu08@gmail.com>
> Date: Sat, 2 Feb 2019 13:23:33 +0900
> Subject: [PATCH] Add: mypaint
> 
> ---
>  gnu/packages/mypaint.scm | 132

I have two more notes (hope I'm not redundant):

We usually just add/modify one package per commit, unless really
necessary. Could you split your contribution into several patches?

The commit message should conform to the GNU Changelog Guides, a link
can be found here:

https://www.gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html#Submitting-Patches

For examples see other commits from the git repository. Could you adapt
your commit's log messages?

Packaging can sometimes be tricky, so please ask the questions you have.

Thank you for your contribution,

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2019-02-05 11:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02  4:44 [bug#34283] [PATCH]Add: mypaint Yoshinori Arai
2019-02-05  5:43 ` swedebugia
2019-02-05  5:52 ` [bug#34283] [PATCH] Add: mypaint Maxim Cournoyer
2019-02-05  9:23   ` Yoshinori Arai
2019-02-05 11:42 ` Björn Höfling [this message]
2019-02-06 11:03   ` [bug#34283] [PATCH]Add: mypaint Yoshinori Arai
2019-02-07 11:13   ` Yoshinori Arai
2019-02-10 19:57     ` Danny Milosavljevic
2019-02-10 22:15       ` Yoshinori Arai
2019-02-08  4:26   ` Yoshinori Arai
2019-02-08  4:30     ` Brett Gilio
2019-02-09 22:54       ` Yoshinori Arai
2019-02-10  1:24         ` Brett Gilio
2019-02-10  2:36           ` Yoshinori Arai
2019-02-08  7:22 ` [bug#34283] [PATCH-1/4]Add: mypaint@1.2.1 Yoshinori Arai
2019-06-28  5:34   ` swedebugia
2019-02-08  7:24 ` [bug#34283] [PATCH-2/4]Add: libmypaint@2.0.0-alpha Yoshinori Arai
2019-02-08  7:25 ` [bug#34283] [PATCH-3/4]Add: mypaint-blushes@2.0.1 Yoshinori Arai
2019-02-08  7:27 ` [bug#34283] [PATCH-4/4]Add: mypaint@2.0.0-alpha.2 Yoshinori Arai
2021-01-15 19:50 ` bug#34283: [PATCH]Add: mypaint Julien Lepiller

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=20190205124255.75e9f343@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=34283@debbugs.gnu.org \
    --cc=kumagusu08@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 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.