all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 54432@debbugs.gnu.org
Cc: 54432-done@debbugs.gnu.org
Subject: [bug#54432] [PATCH] gnu: rtl8812au-aircrack-ng-linux-module: Update to 37e27f9.
Date: Thu, 17 Mar 2022 17:43:40 -0400	[thread overview]
Message-ID: <YjOrjIf4+mzgIUiK@jasmine.lan> (raw)
In-Reply-To: <O2UmIjgVc6Yo_pLmrPfGr7LqIAeCiglHW3gqlWTfArPChZqNOh2LVadtUHGgKFJHvEt7K3RktfMx6vEfm0hnMU5u49tHEgG63JSc6fCQ3ic=@protonmail.com>

On Thu, Mar 17, 2022 at 01:12:33AM +0000, J. Sims via Guix-patches via wrote:
> This fixes issues with Linux 5.17 and adds optimizations for 5.15:
> 
> https://github.com/aircrack-ng/rtl8812au/pull/942
> https://github.com/aircrack-ng/rtl8812au/commit/2f52f84096ae09d36012d455d29b73e6cb37f740
> 
> It also runs `guix style`.
> 
> * gnu/packages/linux.scm (rtl8812au-aircrack-ng-linux-module):
> Update to commit 37e27f9.

Thanks for paying attention to this package!

I pushed the update as commit a28dd4719267914482ee88250a2a6dfbdd81eca7,
although I did omit the style changes in light of Liliana's comments.

https://git.savannah.gnu.org/cgit/guix.git/commit/?id=a28dd4719267914482ee88250a2a6dfbdd81eca7

We can use `guix style` but I prefer that we do it in its own commit,
and maybe even on the entire gnu/packages/linux.scm module at once.

That will make it easier to hide purely stylistic changes from `git
blame`, improving long-term utility of the Git history.

And as Liliana pointed out, maybe `guix style` needs some tweaks before
we use it here.




      parent reply	other threads:[~2022-03-17 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  1:12 [bug#54432] [PATCH] gnu: rtl8812au-aircrack-ng-linux-module: Update to 37e27f9 J. Sims via Guix-patches via
2022-03-17 15:05 ` Liliana Marie Prikler
2022-03-17 21:43 ` Leo Famulari [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=YjOrjIf4+mzgIUiK@jasmine.lan \
    --to=leo@famulari.name \
    --cc=54432-done@debbugs.gnu.org \
    --cc=54432@debbugs.gnu.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.