unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: emma via Guix-patches via <guix-patches@gnu.org>
To: Aaron Covrig <aaron.covrig.us@ieee.org>
Cc: 73523@debbugs.gnu.org
Subject: [bug#73523] Issue 73523 adjustments
Date: Fri, 25 Oct 2024 17:04:10 +0000	[thread overview]
Message-ID: <87h690ru6c.fsf@proton.me> (raw)
In-Reply-To: <20241024203522.45bc3770@mobile-dev>

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

"Aaron Covrig" <aaron.covrig.us@ieee.org> writes:

> Hello big bug,
>
> Thank you for your submission; I modified the patch files as 
> they were
> all garbled when pulled down and failed to apply. I'm curious as 
> to how
> the original commits were created, were they by chance manually 
> copied
> up instead of being sent using git:send-email? Here is a 
> StackOverflow
> on how to setup
> git:send-email: https://stackoverflow.com/q/68238912 it is for 
> gmail
> instead of proton mail, but should give a general idea (and if 
> you
> can't link proton mail this way, you can always create an 
> anonymous
> gmail to send in patches (someone else can chime in if there is 
> an
> alternate way to send patches that is more compatible with 
> proton
> mail/manual copy paste).
>
> Additionally, Guix has additional documentation on how to send 
> in
> patches (and patch series):
> 1. https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html
> 2. https://guix.gnu.org/manual/devel/en/html_node/Sending-a-Patch-Series.html
>
> For future reviewers, I have not extensively checked out the
> patches/verified that they are working; but they should now 
> build
> successfully.
>
> v/r,
>
> Aaron
>
> P.S.
>
> There is also the Mumi interface for sending patches, but I have 
> yet to
> try it personally:
> * 
> https://guix.gnu.org/manual/devel/en/html_node/Debbugs-User-Interfaces.html

hello aaron,
thank you for formatting and the links!
this was my first attempt using git send-email, and was 
encountering several issues, which may be the source of the 
garbling. the original commits were made using the steps laid out 
in 
https://guix.gnu.org/manual/devel/en/html_node/Sending-a-Patch-Series.html, 
but the aforementioned issues had me having to resend the failed 
emails from my proton account. i've since resolved it so i future 
patch submissions should not be garbled.

emma

--
emma
EF515F7D600717781DF9AB2E0FB1CF2867A117F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 881 bytes --]

      reply	other threads:[~2024-10-25 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28  5:00 [bug#73523] [PATCH 0/3] gnu: add pywlroots bigbookofbug--- via Guix-patches via
2024-09-28  6:35 ` [bug#73523] [PATCH 1/3] [PATCH 0/3] gnu: add python-pywlroots bigbookofbug--- via Guix-patches via
2024-09-28  6:35   ` [bug#73523] [PATCH 2/3] [PATCH 2/3] gnu: add pywlroots bigbookofbug--- via Guix-patches via
2024-09-28  6:35   ` [bug#73523] [PATCH 3/3] [PATCH 3/3] " bigbookofbug--- via Guix-patches via
2024-09-28  6:40 ` [bug#73523] [PATCH 2/3] [PATCH 2/3] " bigbookofbug--- via Guix-patches via
2024-10-25  0:20 ` [bug#73523] [PATCH v3 1/3] gnu: Add python-xkbcommon version 1.5.1 Aaron Covrig via Guix-patches via
2024-10-25  0:20   ` [bug#73523] [PATCH v3 2/3] gnu: Add pywayland version 0.4.18 Aaron Covrig via Guix-patches via
2024-10-25  0:20   ` [bug#73523] [PATCH v3 3/3] gnu: Add pywlroots version 0.17.0 Aaron Covrig via Guix-patches via
2024-10-25  0:35 ` [bug#73523] Issue 73523 adjustments Aaron Covrig via Guix-patches via
2024-10-25 17:04   ` emma via Guix-patches via [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

  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=87h690ru6c.fsf@proton.me \
    --to=guix-patches@gnu.org \
    --cc=73523@debbugs.gnu.org \
    --cc=aaron.covrig.us@ieee.org \
    --cc=bigbookofbug@proton.me \
    /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).