From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [lua V3 0/8] lua
Date: Sat, 19 Apr 2014 23:58:38 +0200 [thread overview]
Message-ID: <20140419235838.1fb6d8db@skate> (raw)
In-Reply-To: <20140302000232.6430d956@skate>
Fran?ois,
On Sun, 2 Mar 2014 00:02:32 +0100, Thomas Petazzoni wrote:
> > Francois Perrad (8):
> > luajit: refactor without dont-strip.patch
> > luajit: refactor without shared-lib.patch
> > luajit: handles BR2_PREFER_STATIC_LIB
> > luajit: add host variant
> > luainterpreter: add host variant
> > luarocks: allow to work with host-luainterpreter
>
> For all these patches, and especially the last three ones, I want
> commit logs. I really do appreciate _a lot_ all the work you're doing
> on Lua and Perl, it's really awesome. And I really mean it. But you
> need to work on improving your commit logs. For now, we have no idea
> *why* you're doing these changes.
>
> All the other core developers are doing efforts to write long,
> descriptive commit logs, and experience has shown that they are
> immensely useful 6 or 12 months later when we got back in the Git
> history to understand why things were done. Look at what they do, and
> follow the basic rule of thumb that any non-trivial patch should have
> at least 2 or 3 paragraphs in its commit log explaining *why* the
> change is being made.
>
> At this point, I have no idea what you are doing. I presume patches 4
> and 5 are preparations for patch 6, but I don't understand what patch 6
> is doing, and nowhere it is mentioned why patches 4 and 5 are needed.
Any news about these patches? From this series, we still have patches
4, 5, 6 and 8 pending in patchwork. Could you take into account the
comments that have been made (mainly the strong need for more detailed
commit logs), and resend updated versions on top of master?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-19 21:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 17:23 [Buildroot] [lua V3 0/8] lua Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 1/8] luajit: refactor without dont-strip.patch Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 2/8] luajit: refactor without shared-lib.patch Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 3/8] luajit: handles BR2_PREFER_STATIC_LIB Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 4/8] luajit: add host variant Francois Perrad
2014-03-01 17:47 ` Yann E. MORIN
2014-03-01 18:39 ` Thomas Petazzoni
2014-03-01 21:41 ` Yann E. MORIN
2014-03-01 17:23 ` [Buildroot] [lua V3 5/8] luainterpreter: " Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 6/8] luarocks: allow to work with host-luainterpreter Francois Perrad
2014-03-01 17:23 ` [Buildroot] [lua V3 7/8] ljlinenoise: new package Francois Perrad
2014-03-01 23:15 ` Thomas Petazzoni
2014-03-01 17:23 ` [Buildroot] [lua V3 8/8] lua-iconv: " Francois Perrad
2014-03-01 23:02 ` [Buildroot] [lua V3 0/8] lua Thomas Petazzoni
2014-04-19 21:58 ` Thomas Petazzoni [this message]
2014-04-20 7:38 ` [Buildroot] [UNSURE]Re: " François Perrad
2014-04-20 8:13 ` Thomas Petazzoni
2014-04-20 15:03 ` François Perrad
2014-07-18 17:44 ` [Buildroot] " Thomas Petazzoni
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=20140419235838.1fb6d8db@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox