From: Philip McGrath <philip@philipmcgrath.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Vagrant Cascadian" <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: default tar format for "make dist" and patch file length
Date: Fri, 19 Nov 2021 23:39:21 -0500 [thread overview]
Message-ID: <071f69a4-4e8a-3337-6a84-6ceca5119e6f@philipmcgrath.com> (raw)
In-Reply-To: <87y25kjiwa.fsf@gnu.org>
On 11/19/21 09:54, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>> So, I guess I'm leaning towards making the guix lint check a little more
>> lenient.
>>
>> Thoughts?
>
> That sounds even better, I’m all for it (changing (guix lint) + fixing
> the two remaining issues)!
It might also help to change the warning given by the check.
When a program called "lint" tells me that something is too long, I
understand that to mean that what I've done is generally considered bad
style, but there might be a very good reason to do it in some specific
case. For example, I might exceed a line length guideline to avoid
inserting linebreaks into a URL.
If instead `guix lint` is telling us about a hard limit that will break
things, I think it should say so clearly.
-Philip
next prev parent reply other threads:[~2021-11-20 4:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 0:34 default tar format for "make dist" and patch file length Vagrant Cascadian
2021-11-17 11:32 ` Ludovic Courtès
2021-11-17 22:39 ` Vagrant Cascadian
2021-11-17 23:49 ` Vagrant Cascadian
2021-11-19 14:54 ` Ludovic Courtès
2021-11-20 4:39 ` Philip McGrath [this message]
2021-11-20 5:21 ` Vagrant Cascadian
2021-11-24 21:27 ` Vagrant Cascadian
2021-11-22 2:03 ` Maxim Cournoyer
2021-11-22 11:31 ` Ludovic Courtès
2021-11-22 20:14 ` Maxim Cournoyer
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=071f69a4-4e8a-3337-6a84-6ceca5119e6f@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=vagrant@debian.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 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.