unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marek Benc <merkur32@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add most debian patches to nvi.
Date: Thu, 22 Jan 2015 17:05:47 +0100	[thread overview]
Message-ID: <87r3umby1w.fsf@gnu.org> (raw)
In-Reply-To: <54BFC4FF.5030006@gmail.com> (Marek Benc's message of "Wed, 21 Jan 2015 16:25:51 +0100")

Marek Benc <merkur32@gmail.com> skribis:

> On 01/21/2015 04:03 PM, Ludovic Courtès wrote:
>> I agree with Andreas: there are 20 patches, and that level of patching
>> goes beyond our mission, IMO.
>>
>> I would rather leave it as is if it’s usable, or remove it, or point to
>> a new upstream if there is one.
>
> In that case, I think at least two of the patches should be allowed to
> get in, the ones about the Berkely db library, since it's spewing out
> errors without them. (but the editor itself works)

You mean there are run-time errors without nvi-db4.patch?  What kind?

The second patch is about page sizes apparently.  Do you know what the
deal is?

Two/three patches would be OK, but we need to have an understanding of
why we’re carrying these particular patches.

Thank you!

Ludo’.

  reply	other threads:[~2015-01-22 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54BFBAED.3090502@gmail.com>
2015-01-21 14:44 ` [PATCH] gnu: Add most debian patches to nvi Marek Benc
2015-01-21 15:03   ` Ludovic Courtès
2015-01-21 15:25     ` Marek Benc
2015-01-22 16:05       ` Ludovic Courtès [this message]
2015-01-22 16:39         ` Marek Benc
2015-01-22 16:45           ` Marek Benc
2015-01-22 20:52           ` Ludovic Courtès
2015-01-22 22:17             ` Marek Benc
2015-01-23  8:48               ` Ludovic Courtès
2015-01-20 18:20 Marek Benc
2015-01-21  9:35 ` Andreas Enge

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=87r3umby1w.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=merkur32@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 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).