From: Leo Famulari <leo@famulari.name>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3] gnunet-gtk build-input, homepage (was Re: [PATCH] gnunet.scm -> various changes (description update, adds gnunet-svn, gnunet-gtk-svn, gnurl))
Date: Tue, 29 Mar 2016 16:03:33 -0400 [thread overview]
Message-ID: <20160329200333.GD19843@jasmine> (raw)
In-Reply-To: <87k2kmts7b.fsf@grrlz.net>
On Mon, Mar 28, 2016 at 07:42:16PM +0200, Nils Gillmann wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Mon, Mar 28, 2016 at 05:57:50PM +0200, Nils Gillmann wrote:
> >> From ee326257b613449ca5c0834f7e8f6b8d0840d486 Mon Sep 17 00:00:00 2001
> >> From: Nils Gillmann <niasterisk@grrlz.net>
> >> Date: Mon, 28 Mar 2016 17:49:27 +0200
> >> Subject: [PATCH] gnu: gnunet-gtk: Add build-input and home-page.
> >
> > Can you split this into two patches?
>
> I can, but why should I? Because it's two kinds of changes? I see
> different grouped changes everywhere in the commit logs.
In general I think it's best for unrelated changes to be committed
separately.
next prev parent reply other threads:[~2016-03-29 20:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 16:39 [PATCH] gnunet.scm -> various changes (description update, adds gnunet-svn, gnunet-gtk-svn, gnurl) Nils Gillmann
2016-03-13 21:47 ` Ludovic Courtès
2016-03-14 9:12 ` Nils Gillmann
2016-03-15 15:56 ` Ludovic Courtès
2016-03-15 16:55 ` Nils Gillmann
2016-03-22 11:31 ` Nils Gillmann
2016-03-24 12:39 ` Nils Gillmann
2016-03-28 14:11 ` Nils Gillmann
2016-03-28 15:23 ` [PATCH 1] gnurl (was Re: [PATCH] gnunet.scm -> various changes (description update, adds gnunet-svn, gnunet-gtk-svn, gnurl)) Nils Gillmann
2016-03-28 16:26 ` Leo Famulari
2016-03-28 17:38 ` Nils Gillmann
2016-03-30 23:38 ` Nils Gillmann
2016-03-28 15:43 ` [PATCH 2] gnunet: description " Nils Gillmann
2016-03-28 16:46 ` Leo Famulari
2016-03-28 17:40 ` Nils Gillmann
2016-03-30 21:37 ` Ludovic Courtès
2016-03-30 23:02 ` Nils Gillmann
2016-03-31 6:24 ` Efraim Flashner
2016-03-31 8:30 ` Ludovic Courtès
2016-03-31 8:43 ` Nils Gillmann
2016-03-31 21:28 ` Ludovic Courtès
2016-03-31 22:23 ` Nils Gillmann
2016-03-28 15:57 ` [PATCH 3] gnunet-gtk build-input, homepage " Nils Gillmann
2016-03-28 16:30 ` Leo Famulari
2016-03-28 17:42 ` Nils Gillmann
2016-03-29 20:03 ` Leo Famulari [this message]
2016-03-31 0:06 ` Nils Gillmann
2016-03-29 17:24 ` Efraim Flashner
2016-03-28 16:07 ` [PATCH 3] gnunet-svn " Nils Gillmann
2016-03-28 16:43 ` Leo Famulari
2016-03-28 17:49 ` Nils Gillmann
2016-03-29 0:05 ` Jookia
2016-03-29 7:20 ` Nils Gillmann
2016-03-29 20:01 ` Leo Famulari
2016-03-30 22:48 ` Nils Gillmann
2016-03-31 6:28 ` Efraim Flashner
2016-03-28 17:54 ` Nils Gillmann
2016-03-28 16:17 ` [PATCH 4] gnunet-gtk-svn " Nils Gillmann
2016-03-28 16:45 ` Leo Famulari
2016-03-29 18:17 ` Efraim Flashner
2016-03-29 19:30 ` Nils Gillmann
2016-03-30 22:38 ` Nils Gillmann
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=20160329200333.GD19843@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=niasterisk@grrlz.net \
/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.