All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: akuster <akuster@mvista.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] README: new readme file including main aspects of the project
Date: Mon, 2 Oct 2017 12:05:48 -0500	[thread overview]
Message-ID: <20171002120548.7adef3e92d4cb423f624a97d@linux.intel.com> (raw)
In-Reply-To: <324e7e99-7b13-5e30-36a2-4814be8f7b5b@mvista.com>

 
> Is there any value in providing a sample command:
> 
> git send-patch -M -1 --subject-prefix=Bitbake][PATCH --to
> bitbake-devel@lists.openembedded.org

yes, I think it adds value, specially for new contributors (also this is an effort to reduce patches that get as attachments to the ML).

> 
> - Armin
> - armin
> > +
> > +Mailing list:
> > +
> > +    http://lists.openembedded.org/mailman/listinfo/bitbake-devel
> > +
> > +Source code:
> > +
> > +    http://git.openembedded.org/bitbake/
> 


-- 
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>


      parent reply	other threads:[~2017-10-02 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 15:38 [PATCH 1/3] bitbake-user-manual/bitbake-user-manual: remove YP as build system leonardo.sandoval.gonzalez
2017-10-02 15:38 ` [PATCH 2/3] bitbake-user-manual-metadata: include a space on a append example leonardo.sandoval.gonzalez
2017-10-02 15:38 ` [PATCH 3/3] README: new readme file including main aspects of the project leonardo.sandoval.gonzalez
2017-10-02 16:02   ` akuster
2017-10-02 16:06     ` Alexander Kanavin
2017-10-02 17:04       ` akuster
2017-10-02 17:05     ` Leonardo Sandoval [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=20171002120548.7adef3e92d4cb423f624a97d@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=akuster@mvista.com \
    --cc=bitbake-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 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.