From: Andreas Enge <andreas@enge.fr>
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 4/4] gnu: Add python-requests-mock.
Date: Tue, 15 Sep 2015 19:17:44 +0200 [thread overview]
Message-ID: <20150915171744.GA3054@debian> (raw)
In-Reply-To: <8737yfaahw.fsf@openmailbox.org>
Hello,
On Tue, Sep 15, 2015 at 06:54:51PM +0200, Mathieu Lirzin wrote:
> (sha256
> (base32
> "..."))
like someone else previously on this list I was also puzzled by the discussion
on formatting style (meaning, I did not understand what the indentation to
apply or to avoid is), so I wonder if there are actual rules to be formulated
and applied in case of manual formatting. My impression so far was that
indentation is usually by 2 spaces. So does this mean we now indent only by 1,
or does it depend on the context?
Andreas
next prev parent reply other threads:[~2015-09-15 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 21:23 [PATCH 0/4] Add more dependencies of OpenStack Cyril Roelandt
2015-09-14 21:23 ` [PATCH 1/4] gnu: Add python-oslo.serialization Cyril Roelandt
2015-09-15 16:34 ` Mathieu Lirzin
2015-09-14 21:23 ` [PATCH 2/4] gnu: Add python-oslo.context Cyril Roelandt
2015-09-15 16:36 ` Mathieu Lirzin
2015-09-14 21:23 ` [PATCH 3/4] gnu: Add python-webob Cyril Roelandt
2015-09-15 16:43 ` Mathieu Lirzin
2015-09-15 22:58 ` Cyril Roelandt
2015-09-16 9:03 ` Andreas Enge
2015-09-14 21:23 ` [PATCH 4/4] gnu: Add python-requests-mock Cyril Roelandt
2015-09-15 16:54 ` Mathieu Lirzin
2015-09-15 17:17 ` Andreas Enge [this message]
2015-09-15 17:32 ` Taylan Ulrich Bayırlı/Kammer
2015-09-15 18:36 ` Taylan Ulrich Bayırlı/Kammer
2015-09-16 20:10 ` Andreas Enge
2015-09-16 20:54 ` [PATCH 0/4] Add more dependencies of OpenStack Cyril Roelandt
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=20150915171744.GA3054@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mthl@openmailbox.org \
/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).