workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Kernel development collaboration platform wish list
Date: Thu, 26 Sep 2019 15:41:26 +0200	[thread overview]
Message-ID: <CAMuHMdU73rjaxTwxNaUY9t2LrGsSEJpX4Hz=3AJ2kwbgMYOPoA@mail.gmail.com> (raw)
In-Reply-To: <87muergq3m.fsf@intel.com>

Hi Jani,

On Thu, Sep 26, 2019 at 3:10 PM Jani Nikula <jani.nikula@intel.com> wrote:
> On Thu, 26 Sep 2019, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >   - Quoting a 2000-line patch when commenting on a single line deep down.
>
> I've actually become almost completely immune to that because my mail
> client collapses long quotes by default, thus highlighting the replies.

The Gmail web interface is indeed good at that... Until you want to rebuke
a review comment, and have to go digging...

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2019-09-26 13:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  8:22 Rafael J. Wysocki
2019-09-13 11:13 ` Jani Nikula
2019-09-17 21:58   ` Rafael J. Wysocki
2019-09-18  8:05     ` Jani Nikula
2019-09-18 13:43       ` Steven Rostedt
2019-09-13 11:37 ` Laurent Pinchart
2019-09-13 12:02   ` Geert Uytterhoeven
2019-09-13 12:15     ` Laurent Pinchart
2019-09-13 12:23       ` Geert Uytterhoeven
2019-09-17 22:00         ` Rafael J. Wysocki
2019-10-02  9:30   ` Rafael J. Wysocki
2019-09-17 18:40 ` Stefan Schmidt
2019-09-24  9:43   ` Paolo Bonzini
2019-09-24 12:20     ` Stefan Schmidt
2019-09-17 22:12 ` Rafael J. Wysocki
2019-10-01  3:52   ` Daniel Axtens
2019-10-01  4:50     ` Andrew Donnellan
2019-10-01  5:04       ` Daniel Axtens
2019-09-23 16:20 ` Theodore Y. Ts'o
2019-09-24  1:39   ` Eric Wong
2019-09-24  5:06     ` Greg Kroah-Hartman
2019-10-01  3:58     ` Daniel Axtens
2019-09-26 10:18   ` Geert Uytterhoeven
2019-09-26 11:40     ` Steven Rostedt
2019-09-26 13:39       ` Geert Uytterhoeven
2019-09-28 22:16         ` Steven Rostedt
2019-09-29 16:03           ` Dmitry Vyukov
2019-09-26 13:10     ` Jani Nikula
2019-09-26 13:41       ` Geert Uytterhoeven [this message]
2019-09-26 14:40         ` Jani Nikula
2019-10-02  9:55   ` Rafael J. Wysocki
2019-10-02 14:22     ` Daniel Axtens
2019-10-03  9:23       ` Rafael J. Wysocki

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='CAMuHMdU73rjaxTwxNaUY9t2LrGsSEJpX4Hz=3AJ2kwbgMYOPoA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=jani.nikula@intel.com \
    --cc=jikos@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=rjw@rjwysocki.net \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox