From: Matt <matt@excalamus.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 69977 <69977@debbugs.gnu.org>,
Christian Miller <christian.miller@dadoes.de>
Subject: [bug#69977] [PATCH] doc: doc-Simplify installation instructions
Date: Sat, 06 Apr 2024 10:06:56 +0200 [thread overview]
Message-ID: <18eb2724386.10570c8374299945.4466719558847672340@excalamus.com> (raw)
In-Reply-To: <87le66dsfa.fsf_-_@pelzflorian.de>
---- On Mon, 25 Mar 2024 20:26:17 +0100 pelzflorian (Florian Pelz) wrote ---
> Hi Matt, mostly looks good to me.
That's good to hear! I would like to address your comments in an updated patch set. Unfortunately, I'm struggling to do that. Between my last message and this one, life happened and changes have been made to guix.texi that prevent the application of patch set you've commented on. I've already spent several hours already trying to figure out a better way to revise my suggestions than retyping everything by hand from HEAD. How can git help me in this situation? Or, am I better off scrapping my old patches and just retyping the changes?
next prev parent reply other threads:[~2024-04-06 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5p8yn4p.fsf@dadoes.de>
[not found] ` <18d0e410102.e16898001715108.8020629039859398477@excalamus.com>
[not found] ` <878r4ml93e.fsf@gmail.com>
[not found] ` <18d23870de2.119d4f41c239950.5543896370981537109@excalamus.com>
[not found] ` <18d48373140.10c55a4722276191.1969374822318990762@excalamus.com>
[not found] ` <87r0h5ray4.fsf@gmail.com>
[not found] ` <18dccf417d0.ca418748214075.562011919630800442@excalamus.com>
[not found] ` <87y1bboq2i.fsf@gmail.com>
[not found] ` <18dd741c397.eb3e3c20130225.478777462592413812@excalamus.com>
[not found] ` <18dff5f7ac0.12981499e295073.4475195706110749663@excalamus.com>
[not found] ` <87zfvbgu3q.fsf_-_@pelzflorian.de>
[not found] ` <18e154a064f.10b18ae281601105.807357574739020306@excalamus.com>
[not found] ` <87bk7qnfd5.fsf@pelzflorian.de>
[not found] ` <18e280dc65a.fb9272352515573.111358157668309553@excalamus.com>
[not found] ` <87le6ou5ly.fsf@pelzflorian.de>
[not found] ` <18e46e0150a.126718be4584704.7946677375549431621@excalamus.com>
[not found] ` <87zfuynug6.fsf@pelzflorian.de>
2024-03-24 9:27 ` [bug#69977] [PATCH] doc: doc-Simplify installation instructions (was Re: doc: installation: fix ~root confusion (was Re: doc: Removing much of Binary Installation)) Matt
2024-03-24 9:32 ` [bug#69976] " Matt
[not found] ` <87edbitv7l.fsf@gmail.com>
2024-04-07 8:30 ` bug#69977: " pelzflorian (Florian Pelz)
2024-04-10 2:57 ` [bug#69977] " Maxim Cournoyer
2024-03-25 19:26 ` [bug#69977] [PATCH] doc: doc-Simplify installation instructions pelzflorian (Florian Pelz)
2024-04-06 8:06 ` Matt [this message]
[not found] ` <18ec853a933.df0e6c395339428.1434045801453734872@excalamus.com>
[not found] ` <87cyqutzi7.fsf@pelzflorian.de>
[not found] ` <18ed3bf88ae.d3f47e4a469282.3054417616933929685@excalamus.com>
[not found] ` <87zftwa0ok.fsf@pelzflorian.de>
[not found] ` <87v84dfnpq.fsf_-_@gnu.org>
[not found] ` <18efaa3de65.e04eeaff2622676.5935820749249224648@excalamus.com>
[not found] ` <87zft946gy.fsf@gnu.org>
2024-05-07 17:57 ` [bug#70823] [PATCH] Re: Creating a documentation team? Matt
2024-05-11 13:03 ` bug#70823: " pelzflorian (Florian Pelz)
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=18eb2724386.10570c8374299945.4466719558847672340@excalamus.com \
--to=matt@excalamus.com \
--cc=69977@debbugs.gnu.org \
--cc=christian.miller@dadoes.de \
--cc=pelzflorian@pelzflorian.de \
/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).