All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Michael Halstead <michael@yoctoproject.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: oecommit ml
Date: Mon, 16 Nov 2015 21:52:35 +0100	[thread overview]
Message-ID: <20151116205235.GB2240@jama> (raw)
In-Reply-To: <56465E1B.8040900@yoctoproject.org>

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

On Fri, Nov 13, 2015 at 02:03:07PM -0800, Michael Halstead wrote:
> 
> On 11/13/2015 01:50 PM, Khem Raj wrote:
> >> On Nov 13, 2015, at 1:45 PM, Michael Halstead <michael@yoctoproject.org> wrote:
> >>
> >> Bitbake is disabled with the note:
> >>
> >> # interferes with patchwork sice it sends emails after the patches are
> >> closed
> >> # we could re-enable it if the mails went to someother ml may be
> >> bitbake-commits
> >>
> >> This happens because it was mailing bitbake-devel@lists.openembedded.org
> >>
> >> We can mail openembedded-commits@lists.openembedded.org which would work
> >> fine. Or I can create a bitbake-commits@lists.openembedded.org. Which is
> >> better?
> > I think mailing to openembedded-commits@lists.openembedded.org might be ok. with [bitbake] in message subject for filtering help.
> 
> I've altered the script to include [reponame] in the subject of all
> e-mails and enabled for bitbake.

Seems to be causing some new warnings when pushing to the repo:

OE @ ~/meta-openembedded $ git push origin master
Counting objects: 204, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (193/193), done.
Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done.
Total 204 (delta 147), reused 0 (delta 0)
remote: Scalar found where operator expected at /home/git/git-notify line 140, near "$subject"
remote:         (Missing semicolon on previous line?)
remote: Global symbol "@openembedded" requires explicit package name at /home/git/git-notify line 60.
remote: syntax error at /home/git/git-notify line 140, near "$subject "
remote: Execution of /home/git/git-notify aborted due to compilation errors.
remote: E: failed to find patch for rev 7df2b574f1c4ad445b1656666878cb2ceffca2e0.
remote: E: failed to find patch for rev ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
remote: E: failed to find patch for rev 1ec69e6b3891c01734e57a908a2a675128f126eb.
remote: E: failed to find patch for rev a1d3dce036f80867d30993742d55abb17c6bc057.
...

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

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

  reply	other threads:[~2015-11-16 21:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 23:14 oecommit ml Trevor Woerner
2015-11-13 11:59 ` Martin Jansa
2015-11-13 20:47   ` Khem Raj
2015-11-13 21:39     ` Michael Halstead
2015-11-13 21:41       ` Khem Raj
2015-11-13 21:45         ` Michael Halstead
2015-11-13 21:50           ` Khem Raj
2015-11-13 22:03             ` Michael Halstead
2015-11-16 20:52               ` Martin Jansa [this message]
2015-11-16 20:56                 ` Martin Jansa
2015-11-16 21:56                 ` Michael Halstead
     [not found]                   ` <5659F2A0.7070003@gmail.com>
2016-02-16 16:40                     ` Trevor Woerner
2016-02-16 16:53                       ` Martin Jansa

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=20151116205235.GB2240@jama \
    --to=martin.jansa@gmail.com \
    --cc=michael@yoctoproject.org \
    --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.