From: ng0 <ngillmann@runbox.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH v2] python-lzo + python-lz4
Date: Sat, 24 Sep 2016 21:48:49 +0000 [thread overview]
Message-ID: <8737kp2cla.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160924232828.37da66df@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
>> No, it is not. lzo was number 2 in the original patch couple and is
>> still intended to be applied as such.
>
> I see what you mean but I really doubt that patchwork can see it (also because of the subject it probably will replace the entire set by just this package).
>
Okay, I understand but won't send it again.
I used patchwork for a while, and looking at the past discussions about
alternatives and looking at how much functionality it lacks and almost
no one except ludovic, myself and maybe 2 more people seemed to use
it. So I don't care about patchworks as it is broken. Whoever applies my
patches uses email, no need to adjust my work to a broken tool we
started to test.
Good night
--
ng0
next prev parent reply other threads:[~2016-09-24 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 15:27 [PATCH] python-lzo + python-lz4 ng0
2016-09-24 18:12 ` Danny Milosavljevic
2016-09-24 18:25 ` Danny Milosavljevic
2016-09-24 19:16 ` ng0
2016-09-24 19:58 ` Danny Milosavljevic
2016-09-24 18:27 ` Danny Milosavljevic
2016-09-24 19:54 ` [PATCH v2] " Danny Milosavljevic
2016-09-24 20:22 ` ngillmann
2016-09-24 20:45 ` Danny Milosavljevic
2016-09-24 21:12 ` ng0
2016-09-24 21:28 ` Danny Milosavljevic
2016-09-24 21:48 ` ng0 [this message]
2016-09-25 17:01 ` [PATCH] " Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737kp2cla.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).