From: Sascha Hauer <s.hauer@pengutronix.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Patchwork for Barebox
Date: Mon, 4 Jan 2016 09:59:13 +0100 [thread overview]
Message-ID: <20160104085913.GD13058@pengutronix.de> (raw)
In-Reply-To: <CAGm1_kvRu6hDhcwA7KBGnL+1z4nr6zp++2gOqaH2WDHastEMBg@mail.gmail.com>
Hi Yegor,
On Tue, Dec 29, 2015 at 08:14:26AM +0100, Yegor Yefremov wrote:
> Hi Sascha,
>
> are you going to add Barebox to https://patchwork.ozlabs.org/? I'm
> using this service with Buildroot and it really provides a good patch
> overview.
Would I have to actively use it or is it still useful if it only
collects patches and nobody updates the status to superseeded, applied,
and others?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-01-04 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 7:14 Yegor Yefremov
2016-01-04 8:59 ` Sascha Hauer [this message]
2016-01-04 10:00 ` Yegor Yefremov
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=20160104085913.GD13058@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=yegorslists@googlemail.com \
/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