public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: mark@klomp.org, aburgess@redhat.com, brobecker@adacore.com,
	luis.machado@arm.com, simark@simark.ca, gdb@sourceware.org
Subject: Re: Any concrete plans after the GDB BoF?
Date: Thu, 16 Feb 2023 13:58:22 +0200	[thread overview]
Message-ID: <83zg9d7rfl.fsf@gnu.org> (raw)
In-Reply-To: <Y+4CdURQkxah+Dn6@adacore.com> (message from Joel Brobecker via Gdb on Thu, 16 Feb 2023 14:16:21 +0400)

> Date: Thu, 16 Feb 2023 14:16:21 +0400
> Cc: Andrew Burgess <aburgess@redhat.com>,
>  Joel Brobecker <brobecker@adacore.com>,
>  Luis Machado <luis.machado@arm.com>, Simon Marchi <simark@simark.ca>,
>  Simon Marchi via Gdb <gdb@sourceware.org>
> From: Joel Brobecker via Gdb <gdb@sourceware.org>
> 
> There are not a whole lot of hosting platforms out there, so my concern
> is that, by making email integration a requirement, you're automatically
> eliminating a number of solutions which could answer your requirements
> just as well, only just differently, and from there, lose some great
> features out there.

Please also take into consideration the other side of this: switching
to a web-based discussions makes participation via email all but
impractical.  People tend to answer short answers without quoting the
context, assuming that all the context is visible in the web form
anyway, and that makes email messages undecipherable.  I follow one
such repository, which uses GitHub, for more than a year, and it is
very frustrating.

So if good support for email is not a requirement, we need to consider
the consequences of basically abandoning email entirely.

  reply	other threads:[~2023-02-16 11:58 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 10:47 Luis Machado
2022-10-28 16:16 ` Simon Marchi
2022-10-28 16:51   ` John Baldwin
2022-10-28 16:54     ` Simon Marchi
2022-10-31  9:28   ` Luis Machado
2022-10-31 13:17     ` Simon Marchi
2022-10-31 13:37       ` Joel Brobecker
2022-10-31 14:15         ` Simon Marchi
2022-10-31 17:31           ` Joel Brobecker
2023-02-11 17:13           ` Andrew Burgess
2023-02-12 12:43             ` Mark Wielaard
2023-02-13 11:54               ` Andrew Burgess
2023-02-13 12:52                 ` Luis Machado
2023-02-13 14:24                   ` Tom Tromey
2023-02-13 14:42                     ` Luis Machado
2023-02-13 15:13                   ` Andrew Burgess
2023-02-13 15:23                     ` Luis Machado
2023-02-14  5:48                       ` Joel Brobecker
2023-02-15 14:47                         ` Andrew Burgess
2023-02-16  4:14                           ` Joel Brobecker
2023-02-16  9:51                           ` Mark Wielaard
2023-02-16 10:16                             ` Joel Brobecker
2023-02-16 11:58                               ` Eli Zaretskii [this message]
2023-02-16 13:31                                 ` Joel Brobecker
2023-02-16 15:23                                   ` Eli Zaretskii
2023-02-14 13:07                   ` Mark Wielaard
2023-02-14 14:23                   ` Pedro Alves
2023-02-14 13:00                 ` Mark Wielaard
2023-02-15 14:36                   ` Andrew Burgess
2023-02-13 14:05             ` Tom Tromey
2022-12-15 10:17     ` Luis Machado
2023-01-01 22:02     ` Mark Wielaard
2023-01-20 17:30       ` Tom Tromey
2023-01-20 20:30         ` Tom Tromey
2023-01-27 15:50           ` Lancelot SIX
2023-01-27 23:50             ` Tom Tromey
2023-01-30 17:43               ` Lancelot SIX
2023-01-30 18:46                 ` Mark Wielaard
2023-01-30 21:08                   ` Tom Tromey
2023-02-04 11:36                     ` Mark Wielaard
2023-01-31 10:00                   ` Lancelot SIX
2022-12-13  2:48 ` Frank Ch. Eigler
2023-02-16  8:53 anix

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=83zg9d7rfl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=mark@klomp.org \
    --cc=simark@simark.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).