All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
Date: Thu, 02 Oct 2014 10:54:33 +0200	[thread overview]
Message-ID: <542D12C9.80202@lucaceresoli.net> (raw)
In-Reply-To: <20141001182322.53f6fd68@free-electrons.com>

Dear Thomas,

Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 1 Oct 2014 07:51:16 -0500, Mike Zick wrote:
...
>> Now the noise:
>>
>> I have noticed that recently some of the fix contributors
>> have been including a "few line" quote of a typical error
>> message in addition to the "fix(es): url" comment.
>>
>> As a read-mostly member, I find that new (habit? practice?)
>> very helpful when reading the daily M.L. fix messages.
>>
>> Q:
>> Should there be a discussion on making this additional
>> information a BR "recommended practice" ?
>
> I personally don't have a strong opinion. Since the autobuilder URLs
> are stable, and supposed to be kept around forever, I don't mind seeing
> only the autobuilder URL. But if the submitter decides to include a
> portion of the error message, then fine as well. We could imagine that
> doing this would give a better change of people googling for the error
> message, to stumble across the relevant Buildroot patch rather than
> just the autobuilder results.
>
> Not sure I want to make this a mandatory thing, though. We already have
> a lot of requirements, and doing autobuilder fixes is already not that
> fun, so if we raise the barrier too much, this might discourage
> contributors.

I appreciate when people do that. It makes the commit more
self-explanatory, and it's very handy to search with git log, among
other things.

But I agree it should not be mandatory.

-- 
Luca

  parent reply	other threads:[~2014-10-02  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30 Thomas Petazzoni
2014-10-01 12:51 ` Mike Zick
2014-10-01 16:23   ` Thomas Petazzoni
2014-10-01 16:38     ` Mike Zick
2014-10-02  8:54     ` Luca Ceresoli [this message]
     [not found] ` <542C5684.8050201@posteo.de>
     [not found]   ` <20141001213513.1dedb82c@free-electrons.com>
2014-10-01 19:41     ` Jörg Krause

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=542D12C9.80202@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /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.