From: paul via Guix-patches via <guix-patches@gnu.org>
To: 68857@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Sergey Trofimov" <sarg@sarg.org.ru>,
andrew@trop.in, janneke@gnu.org
Subject: [bug#68857] [PATCH] gnu: home: dotfiles: Avoid creating extra directory in $HOME.
Date: Wed, 7 Feb 2024 01:54:27 +0100 [thread overview]
Message-ID: <d5f0813c-c156-c3d1-3e8b-b6a73b188ae9@autistici.org> (raw)
In-Reply-To: <14bc720d-7fdc-516a-3018-58294c1cafcd@autistici.org>
Hi Janneke,
could you try whether this patch solves
https://issues.guix.gnu.org/68848 for you?
Thank you for your time,
giacomo
next prev parent reply other threads:[~2024-02-07 0:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:15 [bug#68857] gnu: home: dotfiles: Avoid creating extra directory in $HOME paul via Guix-patches via
2024-01-31 22:17 ` [bug#68857] [PATCH] " Giacomo Leidi via Guix-patches via
2024-02-07 0:54 ` paul via Guix-patches via [this message]
2024-02-07 8:05 ` Janneke Nieuwenhuizen
2024-02-07 8:37 ` Janneke Nieuwenhuizen
2024-02-16 17:16 ` paul via Guix-patches via
2024-02-16 18:57 ` Sergey Trofimov
2024-02-16 17:17 ` [bug#68857] [PATCH v2] gnu: home: dotfiles: Properly support both plain and Stow directory layouts Giacomo Leidi via Guix-patches via
2024-02-20 9:37 ` [bug#68857] gnu: home: dotfiles: Avoid creating extra directory in $HOME Ludovic Courtès
2024-02-20 18:38 ` paul via Guix-patches via
2024-02-27 10:17 ` Ludovic Courtès
2024-02-27 11:30 ` Giacomo Leidi
2024-02-27 11:32 ` paul via Guix-patches via
2024-02-27 12:35 ` [bug#68857] [PATCH v3] gnu: home: dotfiles: Properly support both plain and Stow directory layouts Giacomo Leidi via Guix-patches via
2024-03-04 15:46 ` [bug#68857] gnu: home: dotfiles: Avoid creating extra directory in $HOME Ludovic Courtès
2024-03-06 20:51 ` paul via Guix-patches via
2024-03-06 20:52 ` [bug#68857] [PATCH v4] gnu: home: dotfiles: Properly support both plain and Stow directory layouts Giacomo Leidi via Guix-patches via
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=d5f0813c-c156-c3d1-3e8b-b6a73b188ae9@autistici.org \
--to=guix-patches@gnu.org \
--cc=68857@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=goodoldpaul@autistici.org \
--cc=janneke@gnu.org \
--cc=ludo@gnu.org \
--cc=sarg@sarg.org.ru \
/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).