git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Rubén Justo" <rjusto@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Emily Shaffer <nasamuffin@google.com>
Subject: Re: [PATCH 0/2] improve bugreports
Date: Sun, 31 Mar 2024 09:04:06 +0200	[thread overview]
Message-ID: <4f179986-6aca-405a-a122-d0dc058c60d8@gmail.com> (raw)
In-Reply-To: <35de2d76-a03e-4a36-9bb7-6b6ffa4ea123@gmail.com>

On Sat, Mar 23, 2024 at 06:32:35PM +0100, Rubén Justo wrote:
> Let's try to improve the readability of the bug reports we receive.
> 
> The first message should not receive many comments.  The second one
> might.  I'm open to suggestions.
> 
> Thanks.
> 
> Rubén Justo (2):
>   bugreport: add a new line between questions
>   bugreport: add a mark to each proposed questions
> 
>  builtin/bugreport.c  | 16 ++++++++--------
>  t/t0091-bugreport.sh | 12 ++++++++----
>  2 files changed, 16 insertions(+), 12 deletions(-)
> 
> -- 
> 2.44.0.494.g7a0daf3e0d

This series received no response.  One option may be because it went
unnoticed, another because it may not add value.  I'm going to give it
another try and I'll quietly :-) take silence as confirmation of the
second option. 

I'll try to increase the chances of getting a "looks good" by CC'ing
some folks involved in the bugreport tool.

Thanks.


  parent reply	other threads:[~2024-03-31  7:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 17:32 [PATCH 0/2] improve bugreports Rubén Justo
2024-03-23 17:36 ` [PATCH 1/2] bugreport: add a new line between questions Rubén Justo
2024-03-23 17:36 ` [PATCH 2/2] bugreport: add a mark to each proposed questions Rubén Justo
2024-04-01 19:30   ` Kristoffer Haugsbakk
2024-04-01 19:33     ` Rubén Justo
2024-03-31  7:04 ` Rubén Justo [this message]
2024-04-01  3:09   ` [PATCH 0/2] improve bugreports Eric Sunshine
2024-04-01  9:29     ` Junio C Hamano
2024-04-01 19:27     ` Rubén Justo

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f179986-6aca-405a-a122-d0dc058c60d8@gmail.com \
    --to=rjusto@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).