All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Brulebois <kibi@debian.org>
To: Jose R R <jose@metztli-it.com>
Cc: 858849@bugs.debian.org,
	ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Re: Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Date: Wed, 29 Mar 2017 17:48:39 +0200	[thread overview]
Message-ID: <20170329154839.GE17320@mraw.org> (raw)
In-Reply-To: <CAM12Q5QoPtqyE7V0oshZRQOraVJV-82PrYFhytNfwRNBoaRA9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2743 bytes --]

Hi,

Jose R R <jose@metztli-it.com> (2017-03-29):
> With all due respect, 99% of the build code for the debian-installer
> is yours. As well as the build pulls 99% UDEBs from official debian
> repositories.

That doesn't mean that everything built on top of it has to be reported
on Debian mailing lists and bug tracker. See derivative distributions,
they have their own issue tracker, and only forward specific issues.

> i.e., this is a Debian issue, not mine -- as I did not even touch that
> code and/or modules -- which 1 month ago actually did work smooth:
> 
> Netboot debian-installer was unable to load firmware from second USB
> for wifi connection; accordingly, in another virtual screen, I mounted
> the 2nd USB and manually copied the firmware directory onto the
> installer environment /lib. d-i then detected the wifi signal, etc.
> 
> 
> Second, report on this unofficial jessie-backports kernel
> 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
> with module i915, as had been reported by (maintainer?): <
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a
> collateral manner, I am contributing to official debian development.

If you want to reply to submitters/maintainers, reply to specific bug
reports/threads, instead of sending lengthy mails to other people?

> Finally, I am not requesting *any* support. I am simply reporting that
> your d-i pulling official UDEBs actually have been successful, with
> minor modifications and a few extra UDEBs of mine, in my installation
> experience, following Debian documentation guidelines:

I haven't put words in your mouth and suggested you were requesting some
support. I'm just not convinced such reports are useful. If you
encounter specific issues, report specific bug reports against the
relevant component.

debian-boot@ isn't and shouldn't be the destination of each and every
thing connected to, or merely using, Debian Installer.

> "We also encourage installation reports to be sent even if the
> installation is successful, so that we can get as much information as
> possible on the largest number of hardware configurations." <
> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug
> >

Sure, with official images.

> If you are still 'bothered' with my sporadic submissions, I encourage
> you to modify the documentation to specifically exclude the glaring
> omission.

I could be adding a specific “we don't need reiser4-specific reports”
there, but I would hope this isn't needed, since the only submitter of
such reports against images we don't build, publish, or support, seems
to be you.

Thanks for your cooperation.


KiBi.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-03-29 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 16:30 installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64 Metztli Information Technology
2017-03-28  3:00 ` Bug#858849: " Cyril Brulebois
2017-03-29 12:10   ` Jose R R
2017-03-29 15:48     ` Cyril Brulebois [this message]
2017-03-29 16:27       ` Jose R R
2017-03-29 16:46         ` Steve McIntyre

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=20170329154839.GE17320@mraw.org \
    --to=kibi@debian.org \
    --cc=858849@bugs.debian.org \
    --cc=jose@metztli-it.com \
    --cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.