Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2 7/7] samba: upgrade to 4.1.12
Date: Wed, 17 Jun 2015 22:36:32 +0200	[thread overview]
Message-ID: <20150617203632.GA2390@jama> (raw)
In-Reply-To: <1434527353-47017-8-git-send-email-biannm@cn.fujitsu.com>

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

On Wed, Jun 17, 2015 at 03:49:13PM +0800, Bian Naimeng wrote:
> Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
> 
> git send-email will catch error as below
>  fatal: 0002-samba-upgrade-to-4.1.12.patch: 965: patch contains a line longer than 998 characters
> 
> So, please get patch from
> https://github.com/bendaaron/meta-oe-dev/commit/47678ed346a1ce347a64705c76df09d4fa537b0e

I've cherry-picked first 6 patches from here, but this last one fails to
apply, because you're removing samba 3.6.24, but in master we have 3.6.25
since this commit merged more than month ago:

commit 9ac5713b2fcb5ce03693edd40636d8fce3e014d0
Author:     Roy Li <rongqing.li@windriver.com>
AuthorDate: Wed Apr 29 17:25:02 2015 +0800
Commit:     Martin Jansa <Martin.Jansa@gmail.com>
CommitDate: Mon May 11 10:27:28 2015 +0200

    samba: upgrade to 3.6.25

Also this patch only removes 3.6.24, but doesn't add 4.1.12.

Please rebase to latest master and fix the last commit.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-06-17 20:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  7:49 [meta-oe][PATCH v2 0/7] add samba4 and required recipe Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 1/7] waf-samba: add new class Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 2/7] ctdb: add new recipe Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 3/7] libldb: " Bian Naimeng
2015-06-19 15:56   ` Martin Jansa
2015-06-23  5:47     ` Bian, Naimeng
2015-06-23  8:05       ` Martin Jansa
2015-06-24  7:04         ` Bian, Naimeng
2015-07-02  9:01           ` Bian, Naimeng
2015-07-08 10:32             ` Martin Jansa
2015-07-08 11:59               ` Martin Jansa
2015-07-09  0:30                 ` Bian, Naimeng
2015-07-09 15:54                   ` Martin Jansa
2015-07-10  3:49                     ` Bian, Naimeng
2015-07-13 16:17                       ` Martin Jansa
2015-07-17  7:39                         ` Bian, Naimeng
2015-08-03  8:58                           ` Bian, Naimeng
2015-08-03  9:39                             ` Martin Jansa
2015-08-06  6:57                               ` Bian, Naimeng
2015-08-18 10:41                                 ` Martin Jansa
2015-06-17  7:49 ` [meta-oe][PATCH v2 4/7] libtdb: " Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 5/7] libtevent: " Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 6/7] talloc: upgrade to 2.1.1 Bian Naimeng
2015-06-17  7:49 ` [meta-oe][PATCH v2 7/7] samba: upgrade to 4.1.12 Bian Naimeng
2015-06-17 20:36   ` Martin Jansa [this message]
2015-06-18  0:59     ` Bian, Naimeng
2015-06-18 15:31       ` Martin Jansa
2015-06-19  3:16         ` Bian, Naimeng

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=20150617203632.GA2390@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox