From: Mark Reiche <mark.reiche-Mmb7MZpHnFY@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: nilfs-diff
Date: Fri, 03 Aug 2012 22:45:05 +0200 [thread overview]
Message-ID: <1344026705.21631.8.camel@acer.fritz.box> (raw)
Hi list,
I started using nilfs as root file system and I am really impressed and
excited.
Now I'd like to find out the differences (i.e. changed files) between
certain checkpoints. I found an older mail on the old mailing list
("[PATCH 0/9] exprimental API to extract changes between two
checkpoints"), however, the links and git archive referenced there
appear to be dead.
It also appears that this "experimental API" never made it into the
mainstream over the course of the last year :-(
So: Is there a way to find out what changed between the checkpoints?
Thanks,
Mark Reiche
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-08-03 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 20:45 Mark Reiche [this message]
[not found] ` <1344026705.21631.8.camel-y7UOyazmsHdwFLYp8hBm2A@public.gmane.org>
2012-08-04 1:47 ` nilfs-diff Ryusuke Konishi
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=1344026705.21631.8.camel@acer.fritz.box \
--to=mark.reiche-mmb7mzphnfy@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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