From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSION] Use patchwork
Date: Mon, 10 Dec 2018 11:14:20 +0100 [thread overview]
Message-ID: <20181210101419.GA3197@yssyq.m.ilbers.de> (raw)
In-Reply-To: <1a041b08-1827-1bf6-8344-62fa074f7d41@siemens.com>
Hello Claudius,
On Mon, Dec 10, 2018 at 10:17:24AM +0100, Claudius Heine wrote:
> 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?
Thanks for the idea. Yes, I was thinking about that, too. I'll look into that.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2018-12-10 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 9:17 Claudius Heine
2018-12-10 10:14 ` Baurzhan Ismagulov [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=20181210101419.GA3197@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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