All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Amelkin <a.amelkin@yadro.com>
To: Patrick Venture <venture@google.com>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	<gmills@linux.vnet.ibm.com>,  "Tanous, Ed" <ed.tanous@intel.com>
Subject: Re: Proposals for commit log policy
Date: Thu, 6 Sep 2018 16:13:03 +0300	[thread overview]
Message-ID: <47adccd0-a3dc-419f-de07-803a38f6fb6b@yadro.com> (raw)
In-Reply-To: <CAO=notzk_+Q_Pg4xcxzDL=Ux3gyMb2iE0pfSgygDw32wzBHB=w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 510 bytes --]

05.09.2018 02:38, Patrick Venture wrote:
>
>> I fixed it up (by re-writing it in python…it was in Perl) and re-deployed, given
>> all the objections.
> Yay.  No more perl!
Argh! Why do you guys love this ugly python so much? Perl is so much more beautiful and comfortable and kludge-less (like has non-ugly regexps built in)... No semicolons? Indentation defining code block limits? Oh my... Nonetheless, ugly technologies tend to win, it seems.

No need to reply. Just my old-timer's muttering...


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

      reply	other threads:[~2018-09-06 13:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 12:29 Proposals for commit log policy Alexander Amelkin
2018-08-22 15:01 ` Gunnar Mills
2018-08-23  8:23   ` Alexander Amelkin
2018-08-22 20:39 ` Tanous, Ed
2018-08-23  8:44   ` Alexander Amelkin
2018-08-28 22:40     ` Tanous, Ed
2018-08-22 23:58 ` Joel Stanley
2018-08-28 10:29   ` Brad Bishop
2018-08-28 15:43     ` Andrew Geissler
2018-08-28 16:13       ` Patrick Venture
2018-08-28 17:44       ` Gunnar Mills
2018-08-28 22:20         ` Tanous, Ed
2018-08-28 22:43           ` Kun Yi
2018-09-04 20:20           ` Brad Bishop
2018-09-04 23:38             ` Patrick Venture
2018-09-06 13:13               ` Alexander Amelkin [this message]

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=47adccd0-a3dc-419f-de07-803a38f6fb6b@yadro.com \
    --to=a.amelkin@yadro.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=ed.tanous@intel.com \
    --cc=gmills@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.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 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.