all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@infotropique.org>
Cc: 28586@debbugs.gnu.org
Subject: [bug#28586] go-build-system and Syncthing
Date: Mon, 2 Oct 2017 17:42:59 -0400	[thread overview]
Message-ID: <20171002214259.GA25642@jasmine.lan> (raw)
In-Reply-To: <20171002210103.4huokkwrkhanmxig@abyayala>

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

On Mon, Oct 02, 2017 at 09:01:03PM +0000, ng0 wrote:
> Would it be nitpicking to make the requirements of syncthing be individual commits?
> Is this simply okay with initializing the file if it doesn't make any sense
> to have smaller commit steps?

I could do that (not sure if we have a policy or not). But I sent it as
one patch to make it easier to review.

> I'm excited to try the go-build-system out for some of the Go stuff I
> wanted to package.

Please, try it and give feedback :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-02 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 20:36 [bug#28586] go-build-system and Syncthing Leo Famulari
2017-09-24 20:40 ` [bug#28586] [PATCH 1/2] build: Add the Go build system Leo Famulari
2017-09-24 20:40   ` [bug#28586] [PATCH 2/2] gnu: Add Syncthing Leo Famulari
2017-09-25 18:21     ` Leo Famulari
2017-09-25 19:28       ` Leo Famulari
2017-09-26  7:41         ` Ludovic Courtès
2017-09-29 19:24           ` Leo Famulari
2017-10-02 20:23 ` [bug#28586] go-build-system and Syncthing Leo Famulari
2017-10-02 21:01   ` ng0
2017-10-02 21:42     ` Leo Famulari [this message]
2017-10-13  1:47   ` bug#28586: " Leo Famulari
2017-10-13  8:39     ` [bug#28586] " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171002214259.GA25642@jasmine.lan \
    --to=leo@famulari.name \
    --cc=28586@debbugs.gnu.org \
    --cc=ng0@infotropique.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.