Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org
Cc: "Jérôme Poulin" <jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Nilfs features
Date: Mon, 01 Jun 2009 01:20:57 +0900 (JST)	[thread overview]
Message-ID: <20090601.012057.21016829.ryusuke@osrg.net> (raw)
In-Reply-To: <20090526.082051.100027806.ryusuke-sG5X7nlA6pw@public.gmane.org>

Hi,
On Tue, 26 May 2009 08:20:51 +0900 (JST), Ryusuke Konishi wrote:
> Hi,
> On Mon, 25 May 2009 13:46:14 +0400, Dave wrote:
> > In addition to this there doesn't seem to be a way to delete a range of 
> > checkpoints. When i did my restore from my archive, i generated 700+ 
> > useless checkpoints which i had to delete one by one (in a script). It 
> > would be nice to have a 'rmcp 1-100' or 'rmcp -100' or 'rmcp 100-' to 
> > delete a checkpoint range, a start to end.
> 
> Okay, I'll take in this in some form.

For the moment, I've added this feature and pushed it into the git
tree.

(Instead of '1-100', '-100', or '10..', I took notation like '1..100',
 '..100', or '10..' respectively, according to the git tool)

If you would like to try it soon, please see

 http://www.nilfs.org/git/

for download/build information.

I'll include it in the next release of the utility package.

Cheers,
Ryusuke Konishi

  parent reply	other threads:[~2009-05-31 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  9:46 Nilfs features Dave
     [not found] ` <4A1A68E6.50905-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-05-25 23:20   ` Ryusuke Konishi
     [not found]     ` <20090526.082051.100027806.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-05-26  4:54       ` Dave
2009-05-31 16:20       ` Ryusuke Konishi [this message]
     [not found]         ` <20090601.012057.21016829.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-06-02  8:21           ` Dave
     [not found]             ` <4A24E100.8040204-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-02  9:23               ` Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2009-05-30  3:44 Jérôme Poulin
     [not found] ` <debc30fc0905292044r311a2842j53832195d0ef88bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-02  8:31   ` Dave

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=20090601.012057.21016829.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org \
    --cc=jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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