linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [v5] Documentation: bootconfig: Update boot configuration documentation
Date: Thu, 5 Mar 2020 14:26:32 -0500	[thread overview]
Message-ID: <20200305142632.1ed2726d@gandalf.local.home> (raw)
In-Reply-To: <ac1c953b-fa5d-818d-5232-19a28f52f556@web.de>

On Thu, 5 Mar 2020 20:06:47 +0100
Markus Elfring <Markus.Elfring@web.de> wrote:

> >>>> Which of the possibly unanswered issues do you find not concrete enough so far?  
> >>>
> >>> e.g.:  
> >>>>>>  Will the clarification become more constructive for remaining challenges?  
> >>
> >> Do you expect that known open issues need to be repeated for each patch revision?  
> >
> > Ideally not, but not very much is ideal.  
> 
> Did you notice any aspects where I would be still looking for more helpful answers?

What does that even mean?

> 
> 
> > IOW, it is sometimes required (if one cares enough; sometimes
> > one just gives up).  
> 
> I find this communication detail unfortunate occasionally.

Well, it's better than slamming one's head into their desk.

> 
> 
> >> How do you think about the desired tracking of bug reports
> >> also for this software?  
> …
> > Masami seems to be responsive.  
> 
> The involved contributors show different response delays, don't they?
> 

Of course! Masami is in Japan, and is probably sleeping right now. That's
what happens when you work in a global environment.

-- Steve

  parent reply	other threads:[~2020-03-05 19:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:44 [PATCH v5 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-05  6:44 ` [PATCH v5] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-05  7:01   ` Randy Dunlap
2020-03-05  9:33     ` [v5] " Markus Elfring
2020-03-05 16:06       ` Randy Dunlap
2020-03-05 17:30         ` Markus Elfring
2020-03-05 17:48           ` Randy Dunlap
2020-03-05 17:56             ` Markus Elfring
2020-03-05 18:39               ` Randy Dunlap
2020-03-05 18:43                 ` Markus Elfring
2020-03-05 18:57                   ` Randy Dunlap
2020-03-05 19:06                     ` Markus Elfring
2020-03-05 19:19                       ` Randy Dunlap
2020-03-05 19:34                         ` Markus Elfring
2020-03-05 19:26                       ` Steven Rostedt [this message]
2020-03-05 20:26                         ` Markus Elfring
2020-03-05 20:57                           ` Steven Rostedt
2020-03-05 19:00                   ` Steven Rostedt
2020-03-05 19:14                     ` Markus Elfring
2020-03-05 19:25                       ` Steven Rostedt
2020-03-05 20:10                         ` Markus Elfring
2020-03-05 20:56                           ` Steven Rostedt
2020-03-05 21:26                             ` Markus Elfring
2020-03-05 10:32     ` [PATCH v5] " Masami Hiramatsu
2020-03-05 13:36     ` [PATCH v5.1] " Masami Hiramatsu
2020-03-05 14:00       ` Markus Elfring
2020-03-06  1:51         ` Masami Hiramatsu
2020-03-06  9:34           ` Markus Elfring
2020-03-06 14:04             ` Masami Hiramatsu
2020-03-06 18:14               ` [v5.1] " Markus Elfring
2020-03-06 18:40               ` Markus Elfring
2020-03-14  8:45       ` [PATCH v5.1] " Markus Elfring
2020-03-05  9:22   ` [PATCH v5] " Markus Elfring
2020-03-05 10:19   ` Markus Elfring
2020-03-05 16:07     ` Randy Dunlap
2020-03-05  9:10 ` [v5 0/1] Documentation: bootconfig: Documentation updates Markus Elfring

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=20200305142632.1ed2726d@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=Markus.Elfring@web.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).