9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #4: Making Backups
Date: Mon, 25 Apr 2022 07:37:21 +0000	[thread overview]
Message-ID: <d8501e378110871e4c7aa85bba182f2d@a-b.xyz> (raw)
In-Reply-To: <AED1E9E6B2E05EC74C94C5E79CA23505@9lab.org>

> clone⁽¹⁾ is usually one of the first things I put on
> a machine as I am not aware of a more convenient way
> to copy file hierarchies from A to B (thanks kvik) in
> a fast way.

Glad my shitware is of help to you. :)

> Has clone been considered as an addition to the 9front
> base system in the past?

I'd veto this on the basis of it (clone) being incomplete
as a replacement for disk/mkfs for the described backup
managing task. Primarily, it has to (1) learn to read the
"job" in the form of a proto file, and (2) be able to filter
out "up to date" files.

The current code kinda sucks (don't you judge me!) which
makes these two things more difficult to implement than ideal.

Writing a fresh version which takes into account the above
points should be easy with the benefit of hindsight.
Unfortunately I'm quite busy typing C++ at work which leaves
me with very little motivation to touch computers in my spare
time.

Sorry.

  reply	other threads:[~2022-04-25  7:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23  4:22 Stanley Lieber
2022-04-25  6:21 ` igor
2022-04-25  7:37   ` kvik [this message]
2022-04-25 10:31     ` sirjofri
2022-04-25 10:39       ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-04-25 12:32         ` hiro
2022-04-26 11:42       ` qwx
2022-04-26 14:23         ` Steve Simon
2022-04-27 23:30         ` sl

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=d8501e378110871e4c7aa85bba182f2d@a-b.xyz \
    --to=kvik@a-b.xyz \
    --cc=9front@9front.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.
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 NNTP newsgroup(s).