From: Denys Dmytriyenko <denys@ti.com>
To: <meta-ti@yoctoproject.org>
Subject: Commit notifications
Date: Wed, 15 Feb 2017 15:27:57 -0500 [thread overview]
Message-ID: <20170215202756.GB19009@edge> (raw)
All,
With patches now often being merged to 4 branches (krogoth, morty, morty-next
and master), the volume of automatic commit notifications is getting rather
high... Do people think I should move those to a separate dedicated list off
of main meta-ti list?
--
Denys
next reply other threads:[~2017-02-15 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:27 Denys Dmytriyenko [this message]
2017-03-01 21:18 ` Commit notifications Denys Dmytriyenko
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=20170215202756.GB19009@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.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.