all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>,
	Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: milkytracker: Update upstream location.
Date: Fri, 11 Nov 2016 11:14:16 +0000	[thread overview]
Message-ID: <87fumyqnef.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87shqyjqlg.fsf@we.make.ritual.n0.is>

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

ng0 <ng0@we.make.ritual.n0.is> writes:

>
> I'm irritated that 1b35fea19f4675e9491479c4fb09a626357716db ended
> up with the remark "reported by ng0" as I did not report it, I've
> sent a patch.

Sorry about that. After reducing the patch to two lines, there was still
a copyright line added, which felt out-of-place for a simple fact
update. So I was left with the choice of keeping it (probably the best
option in hindsight), removing it (is that even legal), or submitting
the patch as myself, sidestepping the problem.

To be fair, if you had checked their "Downloads" page before changing it
to use Github, the only thing left for me to do would be to apply it ;-)

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

  reply	other threads:[~2016-11-11 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 15:46 [PATCH] gnu: milkytracker: Update upstream location, files ng0
2016-11-10 15:46 ` [PATCH] gnu: milkytracker: Update upstream location ng0
2016-11-10 16:53   ` Christopher Allan Webber
2016-11-11  9:47     ` ng0
2016-11-11 11:14       ` Marius Bakke [this message]
2016-11-10 16:35 ` [PATCH] gnu: milkytracker: Update upstream location, files Marius Bakke
2016-11-11 13:25   ` ng0
2016-11-11 13:54     ` Marius Bakke

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=87fumyqnef.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.