all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Simplify LLVM build.
Date: Mon, 24 Aug 2015 11:50:32 -0400	[thread overview]
Message-ID: <87oahwofcn.fsf@netris.org> (raw)
In-Reply-To: <87y4h19lhu.fsf@igalia.com> (Andy Wingo's message of "Mon, 24 Aug 2015 09:46:53 +0200")

Andy Wingo <wingo@igalia.com> writes:

> On Fri 21 Aug 2015 23:16, Mark H Weaver <mhw@netris.org> writes:
>
>> Andy Wingo <wingo@igalia.com> writes:
>>
>>> If Guix has additional requirements they should be indicated
>>> somewhere; did I miss the document?
>>
>> No, you didn't miss it.  We have a lot to do, and writing precise
>> documentation of our coding standards is not something we've yet found
>> time for.  I'm not sure it's something that could be precisely
>> documented even if we tried.
>
> I'm pretty sure many things could be documented.  Specifically the rules
> about the commit line formatting and the format of messages adding new
> packages or upgrading packages have been explained enough times that it
> is wasting your time not to put them in a document :)

Well, okay, you have a good point :)

> Probably they should be put into some automatic linter as well.

That would be more difficult.

>> I'd like to push your commit with Eric's proposed commit log.
>> Is that okay?
>
> Sure!  Thank you Mark :)

Pushed.  Thanks to you both!

     Mark

      reply	other threads:[~2015-08-24 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  6:27 [PATCH] gnu: Simplify LLVM build Andy Wingo
2015-08-17  8:43 ` Eric Bavier
2015-08-17 13:56   ` Andy Wingo
2015-08-21 21:16     ` Mark H Weaver
2015-08-24  7:46       ` Andy Wingo
2015-08-24 15:50         ` Mark H Weaver [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=87oahwofcn.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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 external index

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

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.