From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [DISCUSSION] Use patchwork
Date: Mon, 10 Dec 2018 10:17:24 +0100 [thread overview]
Message-ID: <1a041b08-1827-1bf6-8344-62fa074f7d41@siemens.com> (raw)
Hi,
maybe we could setup patchwork[1] in order to improve the handling of
patches.
I currently struggle with knowing which patch needs to be reviewed, and
which patchset is superseded etc. It might also help to prevent patches
from being forgotten etc.
What are your thoughts?
Kind regards,
Claudius
[1] https://github.com/getpatchwork/patchwork
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next reply other threads:[~2018-12-10 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 9:17 Claudius Heine [this message]
2018-12-10 10:14 ` Baurzhan Ismagulov
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=1a041b08-1827-1bf6-8344-62fa074f7d41@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.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