unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Danny O'Brien" <danny@spesh.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 61263@debbugs.gnu.org
Subject: [bug#61263] [PATCH] gnu: dbacl: Fix failing check phase.
Date: Sat, 4 Feb 2023 23:53:29 -0500	[thread overview]
Message-ID: <CAAkY2sfwK1-4ZNgyzMkTQ5ZrPWtSfgeOuVQiq6abDBgq1yQpWQ@mail.gmail.com> (raw)
In-Reply-To: <1FBBFFA5-565C-4CD2-8744-518652E1DC53@tobias.gr>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On Sat, Feb 04, 2023 at 2:07 AM, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> Hi Danny,
>
> Low-quality review incoming.
>
> I've merged the two duplicate-looking bugs 61263 & 61270. What happened?
>


I think I didn't spot that the earlier submission went through.


> When adding new patch files, you need also add them to gnu/local.mk's
> sorted dist_patch_DATA list. Thanks for submitting it upstream!
>

Ah, will do!



Reviewing the rest in K-9 is difficult because of the sweeping indentation
> changes. Could you submit a v2 without them?
>
> I suspect I'm disagreeing with 'guix style' and not with you, but the
> 'source' , '#t', and comment changes are steps back IMO (that poor "/"!).
>
> As a rule, there's no requirement to blanket reformat existing code in
> Guix. 'guix style' isn't there yet.
>
> Removing the obsolete '#t's entirely is welcome though—in a separate
> commit.
>
> Thanks!
>
> T G-R
>
> Sent on the go. Excuse or enjoy my brevity.
>


Yep, that was all due to `guix style` — the instructions say to run it, but
that may be different if it's just tweaking an existing hand-crafted
package description. I'll re-submit.

Thanks for your suggestions!

d.

[-- Attachment #2: Type: text/html, Size: 3021 bytes --]

  reply	other threads:[~2023-02-05  4:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04  5:08 [bug#61263] [PATCH] gnu: dbacl: Fix failing check phase danny
2023-02-04 10:07 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-05  4:53   ` Danny O'Brien [this message]
2023-03-04 16:37     ` [bug#61263] bug#61270: " Ludovic Courtès
2023-03-05  7:24       ` [bug#61270] " Danny O'Brien via Guix-patches via
2023-03-22  2:13         ` bug#61263: bug#61270: " 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

  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=CAAkY2sfwK1-4ZNgyzMkTQ5ZrPWtSfgeOuVQiq6abDBgq1yQpWQ@mail.gmail.com \
    --to=danny@spesh.com \
    --cc=61263@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).