Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libmemcached: disable documentation
Date: Wed, 15 Jul 2015 00:54:46 +0200	[thread overview]
Message-ID: <20150715005446.5fafbc8e@free-electrons.com> (raw)
In-Reply-To: <1431382192-3141-1-git-send-email-romain.naour@openwide.fr>

Dear Romain Naour,

On Tue, 12 May 2015 00:09:52 +0200, Romain Naour wrote:
> libmemcached fail to build the documentation/man due to
> an python sphinx error.
> 
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> This is probably an error throw by my Fedora 21 host.
> ---
>  .../libmemcached/0004-disable-doc-and-man.patch    | 37 ++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
>  create mode 100644 package/libmemcached/0004-disable-doc-and-man.patch

I don't really like the patch because it's clearly not upstreamable,
but:

 1/ The existing other 3 patches we have are also non-upstreamable

 2/ Upstream uses the Bazaar version control system, which is probably
    the most efficient thing you can do to make sure nobody will be
    interested in contributing to your project :-)

So, let's not care about this patch not being in an upstreamable state.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-07-14 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 22:09 [Buildroot] [PATCH] package/libmemcached: disable documentation Romain Naour
2015-07-14 22:54 ` Thomas Petazzoni [this message]

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=20150715005446.5fafbc8e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox