unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 4/6] gnu: linux-libre-beagle-bone-black: Remove kernel variant.
Date: Mon, 26 Sep 2016 20:28:34 +0200	[thread overview]
Message-ID: <CAL1_immdVk4RzWARMYpNiGxqtnVyJp2C+q8iJGHxvW7AdcwEAA@mail.gmail.com> (raw)
In-Reply-To: <CAEwRq=qkG5dO2NgCkfyR4T3=rGtyv=gP5J7yy7k9iL5W0=_J6A@mail.gmail.com>

> Recently, on another project,  I came across a line of code which I
> was pretty sure was pointless.

The guy who wrote that line should have included a comment in that
case. The git history isn't a replacement for code commenting. Code
needs to be readable without looking at it's history.

  reply	other threads:[~2016-09-26 18:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 10:34 [PATCH 1/6] gnu: Add picocom David Craven
2016-09-26 10:34 ` [PATCH 2/6] gnu: %default-extra-linux-options: Remove redundant options David Craven
2016-09-29  8:40   ` Ludovic Courtès
2016-09-29  8:53     ` David Craven
2016-09-29 10:33       ` David Craven
2016-09-29 12:35         ` Ludovic Courtès
2016-09-26 10:34 ` [PATCH 3/6] gnu: make-linux-libre: Install device tree files David Craven
2016-09-26 10:34 ` [PATCH 4/6] gnu: linux-libre-beagle-bone-black: Remove kernel variant David Craven
2016-09-26 13:23   ` John Darrington
2016-09-26 13:25     ` David Craven
2016-09-26 14:24     ` Vincent Legoll
2016-09-26 15:57       ` Ricardo Wurmus
2016-09-26 16:49       ` John Darrington
2016-09-26 16:57         ` Vincent Legoll
2016-09-26 17:31         ` Leo Famulari
2016-09-26 18:00           ` John Darrington
2016-09-26 18:06             ` David Craven
2016-09-26 18:22               ` Vincent Legoll
2016-09-26 18:28                 ` David Craven [this message]
2016-09-26 18:34               ` Leo Famulari
2016-09-28 21:13             ` Ludovic Courtès
2016-09-27 10:47         ` Tobias Geerinckx-Rice
2016-09-28  0:14         ` Mark H Weaver
2016-09-28  6:16           ` John Darrington
2016-09-28 21:15           ` Ludovic Courtès
2016-09-28 21:11       ` Ludovic Courtès
2016-10-03 12:49         ` Vincent Legoll
2016-10-03 15:40           ` Ludovic Courtès
2016-10-04 14:32             ` Vincent Legoll
2016-09-26 10:34 ` [PATCH 5/6] gnu: make-u-boot-package: Add files-to-install argument David Craven
2016-09-26 12:39   ` Danny Milosavljevic
2016-09-26 13:38     ` David Craven
2016-09-26 13:41       ` David Craven
2016-09-26 14:04         ` Danny Milosavljevic
2016-09-26 14:07           ` David Craven
2016-09-26 22:28             ` Danny Milosavljevic
2016-10-07  8:19               ` David Craven
2016-10-07  9:26                 ` Danny Milosavljevic
2016-09-26 10:34 ` [PATCH 6/6] gnu: make-u-boot-package: Don't cross compile on arm David Craven
2016-09-26 17:24 ` [PATCH 1/6] gnu: Add picocom Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL1_immdVk4RzWARMYpNiGxqtnVyJp2C+q8iJGHxvW7AdcwEAA@mail.gmail.com \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).