Re: This is how you import a mailing list archives (e.g. guix-patches) into mu4e

2022-12-06 Thread Kyle Meyer
zimoun writes: > I fetch from yhetil.org (Git) and then convert to MailDir because I use > Notmuch as indexer (and reader :-)). And I do not want to duplicate the > storage. Therefore, after fetching and converting, the Git repo is > garbage collected, > > --8<---cut here

Re: This is how you import a mailing list archives (e.g. guix-patches) into mu4e

2022-12-05 Thread Kyle Meyer
On 12/05/22 09:45:41 +0100, zimoun wrote: > Personally, I use “git clone” from a public-inbox instance [1]. > > git clone --mirror https://yhetil.org/guix-patches/1 \ > guix-patches/git/1.git > > where ’1’ can be also replace by ’0’ for the very old ones. In the case of guix-patc

Re: Exporting patches without prerequisite patch id

2022-08-03 Thread Kyle Meyer
kiasoc5 writes: > I have some commits on my local guix repo like this: > > (master) HEAD -> A -> B -> C > > When I do `git format-patch -3 --base=auto` I get prerequisite patch > ids in some of the patches. But I want to each patch to depend only on > HEAD. In other words I want to export patches

Re: Using emacs library with guix environment

2021-10-06 Thread Kyle Meyer
jgart writes: > I'm only able to properly source the library into the environment if I run > the following: > > `guix environment emacs-commander --ad-hoc emacs-commander` > > Why do I have to provide emacs-commander twice to the environment command? I believe the key package that the first emac

Re: Workflow with mu4e + magit for sending patchsets to guix?

2020-11-30 Thread Kyle Meyer
Pierre Neidhardt writes: > --8<---cut here---start->8--- > (defvar ambrevar/known-mailing-list-archives > '(("help-guix@gnu.org" . "guix-user") > ("guix-de...@gnu.org" . "guix-devel") > ("debbugs.gnu.org" . "guix-bugs")) > "Alist of mail adresses and

Re: Workflow with mu4e + magit for sending patchsets to guix?

2020-11-17 Thread Kyle Meyer
zimoun writes: > On Mon, 16 Nov 2020 at 21:36, Kyle Meyer wrote: > >>> 4. !! send-email --to=guix-patc...@gnu.org -cover-letter.patch >>> 5. Wait and refresh my inbox >>> 6. !! send-email --to=12...@gnu.org 000?-*.patch >> >> Yeah, 4-6 are tri

Re: Workflow with mu4e + magit for sending patchsets to guix?

2020-11-17 Thread Kyle Meyer
Kyle Meyer writes: >> C-m l > > If you follow the convention of writing a cover letter only for > multi-patch series, you can drop the 'C-m l' because by default git will > generate a cover letter when there is more than one commit. Sorry, I was mistaken: gen

Re: Workflow with mu4e + magit for sending patchsets to guix?

2020-11-16 Thread Kyle Meyer
zimoun writes: > Hi Chris > > +CC Kyle since they probably knows the status [1]. Sorry, I have no good news for you :/ > On Mon, 16 Nov 2020 at 15:28, Christopher Lemmer Webber > wrote: > >> I've been making patchset series of emails to guix-patches manually. >> I'm sure this is the wrong thin