From: Leo Famulari <leo@famulari.name>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/3] Add Attic backup program
Date: Sun, 30 Aug 2015 23:52:05 -0400 [thread overview]
Message-ID: <1440993125.1086304.370243193.32BA2E0C@webmail.messagingengine.com> (raw)
In-Reply-To: <87613w8ru8.fsf@gmail.com>
Thanks for your comments!
On Sun, Aug 30, 2015, at 16:05, Alex Kost wrote:>
> Ah, sorry, I read this after replying to your 'llfuse' patch. I agree
> on separating fuse module, as there are several fuse-related packages
> (sshfs-fuse, unionfs-fuse, fuse-exfat).
The reasoning behind meta-modules like python.scm, backup.scm, or a
potential fuse.scm is not clear to me — there are some Python programs
in their own modules or in other meta-modules. Ditto for prepending
"python-" to certain module names and not others.
Anyway, if there is a consensus on what to do about llfuse, I will
submit a revised patchset.
Right now it seems that the choices are either:
1) llfuse.scm (this patchset would do this)
2) put it in python.scm as python-llfuse
3) create fuse.scm and put it in there along with some other
fuse-related modules.
In the meantime, I will prepare revisions to address your other
comments.
next prev parent reply other threads:[~2015-08-31 3:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 17:16 [PATCH 0/3] Add Attic backup program Leo Famulari
2015-08-26 17:16 ` [PATCH 1/3] gnu: Add llfuse Leo Famulari
2015-08-30 19:57 ` Alex Kost
2015-08-31 11:52 ` Ludovic Courtès
2015-09-01 21:04 ` Leo Famulari
2015-08-26 17:16 ` [PATCH 2/3] gnu: Add python-msgpack Leo Famulari
2015-08-30 19:57 ` Alex Kost
2015-08-31 11:55 ` Ludovic Courtès
2015-08-26 17:16 ` [PATCH 3/3] gnu: Add Attic Leo Famulari
2015-08-30 19:58 ` Alex Kost
2015-09-01 21:06 ` Leo Famulari
2015-08-30 20:05 ` [PATCH 0/3] Add Attic backup program Alex Kost
2015-08-31 3:52 ` Leo Famulari [this message]
2015-08-31 11:57 ` Ludovic Courtès
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=1440993125.1086304.370243193.32BA2E0C@webmail.messagingengine.com \
--to=leo@famulari.name \
--cc=alezost@gmail.com \
--cc=guix-devel@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.