mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Levente Kurusa <levex@linux.com>
Cc: "Teodora Băluţă" <teobaluta@gmail.com>,
	"David Lang" <david@lang.hm>, "Dave Jones" <davej@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Subject: Re: [RFC] QR encoding for Oops messages
Date: Tue, 8 Apr 2014 13:20:22 -0400	[thread overview]
Message-ID: <20140408172022.GC13102@titan.lakedaemon.net> (raw)
In-Reply-To: <534418C8.6080105@linux.com>

On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote:
> On 04/07/2014 05:20 PM, Jason Cooper wrote:
> > On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote:
> >> Oh and another suggestion, I think placing it in the bottom-right
> >> corner would be better since then we wouldn't overwrite some of
> >> the timestamps and messages.
> > 
> > The real text is still sent to the (hopefully written to disk) logs.  If
> > a user (or distro) builds with this feature, I would think centered and
> > scaled for ease of scanning would be highest priority.
> 
> Yup, I'll be traveling on the train a lot this week, so I'll
> have plenty of time to implement scaling and centering. Maybe
> we could also implement this:
> 
> qr_oops=center   (center the QR code with scale 1)
> qr_oops=center,3 (center the QR code with scale 3)
> 
> 'center' could also be 'topleft', 'bottomright', etc.
> Or just remain at the KISS rule? (keep it simple)
> 
> Any objections?

KISS. ;-)

Iff we find we need the feature later, we can always add qr_oops_pos or
similar.

thx,

Jason.

  reply	other threads:[~2014-04-08 17:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 21:59 Teodora Baluta
2014-03-18 21:49 ` Matthew Garrett
2014-03-19 20:09   ` Teodora Băluţă
2014-03-19 18:03 ` Borislav Petkov
2014-03-19 20:18   ` Teodora Băluţă
2014-03-19 20:18 ` Dave Jones
2014-03-19 20:28   ` Levente Kurusa
2014-03-19 20:50     ` Teodora Băluţă
2014-03-19 20:51       ` Teodora Băluţă
2014-03-19 21:17       ` Levente Kurusa
2014-03-19 20:38   ` Teodora Băluţă
2014-03-21 13:28     ` Jason Cooper
2014-03-22 17:09       ` Levente Kurusa
2014-03-22 18:20         ` Teodora Băluţă
2014-03-22 18:29           ` Levente Kurusa
2014-03-23 11:51             ` Levente Kurusa
2014-03-23 19:38           ` Jason Cooper
2014-03-30 10:17             ` Levente Kurusa
2014-04-01 14:20               ` Jason Cooper
2014-04-01 21:07                 ` Teodora Băluţă
2014-04-03 20:21                   ` Levente Kurusa
2014-04-04 15:12                     ` Jason Cooper
2014-04-04 15:42                       ` Levente Kurusa
2014-04-03 20:57                 ` David Lang
2014-04-04 15:15                   ` Jason Cooper
2014-04-04 16:17                     ` Levente Kurusa
2014-04-04 21:42                       ` Teodora Băluţă
2014-04-05  9:11                         ` Levente Kurusa
2014-04-07 15:20                           ` Jason Cooper
2014-04-08 15:42                             ` Levente Kurusa
2014-04-08 17:20                               ` Jason Cooper [this message]
2014-04-08 17:29                                 ` Levente Kurusa
2014-04-13 20:43                                   ` Levente Kurusa

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=20140408172022.GC13102@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=davej@redhat.com \
    --cc=david@lang.hm \
    --cc=levex@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=teobaluta@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®