All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: David Vincent <freesilicon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for openssh: Make sshd-config a package
Date: Mon, 23 Jan 2017 11:56:26 -0600	[thread overview]
Message-ID: <b8c86614-375b-cfca-8863-9ee9bb7d59d6@linux.intel.com> (raw)
In-Reply-To: <3671180.cChI1EznzE@crde-port-20.cahors.local>



On 01/23/2017 10:39 AM, David Vincent wrote:
> On lundi 23 janvier 2017 10:08:04 CET Leonardo Sandoval wrote:
>> David, This is what I get from the command line
>>
>> oe-core$ git pw mbox 4904 | git apply --check
>> error: documentation/ref-manual/ref-variables.xml: No such file or directory
>>
>> Meaning that you have a patch on your series that is targeted for the
>> documentation folder, which is not part of the oe-core project. The
>> latter need to be sent to:
>>
>> documentation:
>>       Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
>>       Mailing list: yocto@yoctoproject.org
>>
> OK, my bad, I patched directly against my poky clone. I didn't know that
> documentation was handled elsewhere. So, I will resubmit it removing the
> latest patch.
>
> But since these patches are related, is there a specific procedure to follow ?
> I didn't found anything in the contribution guidelines on the wiki...
I do not think so. Go ahead and send to the patches to the correct ML 
and perhaps include a cover letter indicating the patch relationship.

> Sorry for the inconvenience,
no problem.

By the way, there is enhancement (to be included during 2.3) that will 
target this type of problem: patch sent to the wrong ML; once 
implemented, the fail report will be more specific.

> David
>



  reply	other threads:[~2017-01-23 17:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 14:55 [PATCH 0/4] openssh: Make sshd-config a package David Vincent
2017-01-23 14:55 ` [PATCH 1/4] openssh: Package server configuration David Vincent
2017-01-23 14:55 ` [PATCH 2/4] core-image: Set default sshd configuration David Vincent
2017-01-23 14:55 ` [PATCH 3/4] rootfs-postcommands: Modify ssh-related commands David Vincent
2017-01-23 14:55 ` [PATCH 4/4] ref-manual: Add SSHD_CONFIG David Vincent
2017-01-23 15:23 ` ✗ patchtest: failure for openssh: Make sshd-config a package Patchwork
2017-01-23 15:45   ` David Vincent
2017-01-23 16:08     ` Leonardo Sandoval
2017-01-23 16:39       ` David Vincent
2017-01-23 17:56         ` Leonardo Sandoval [this message]
2017-01-24  8:43 ` [PATCH 0/3] " David Vincent
2017-01-24  8:43   ` [PATCH 1/3] openssh: Package server configuration David Vincent
2017-01-24  8:43   ` [PATCH 2/3] core-image: Set default sshd configuration David Vincent
2017-01-24  8:43   ` [PATCH 3/3] rootfs-postcommands: Modify ssh-related commands David Vincent
2017-01-24  9:07 ` [PATCH v2 0/3] openssh: Make sshd-config a package David Vincent
2017-01-24  9:07   ` [PATCH 1/3] openssh: Package server configuration David Vincent
2017-01-24  9:07   ` [PATCH 2/3] core-image: Set default sshd configuration David Vincent
2017-01-24  9:07   ` [PATCH 3/3] rootfs-postcommands: Modify ssh-related commands David Vincent
2017-01-24 19:07   ` [PATCH v2 0/3] openssh: Make sshd-config a package Khem Raj
2017-01-25  7:58     ` David Vincent
2017-02-02 10:30   ` [PATCH v3 " David Vincent
2017-02-02 10:30     ` [PATCH v3 1/3] openssh: Package server configuration David Vincent
2017-02-02 10:30     ` [PATCH v3 2/3] core-image: Set default sshd configuration David Vincent
2017-02-02 10:30     ` [PATCH v3 3/3] rootfs-postcommands: Modify ssh-related commands David Vincent

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=b8c86614-375b-cfca-8863-9ee9bb7d59d6@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=freesilicon@gmail.com \
    --cc=openembedded-core@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 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.