Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature-request] Adding a few new formatting options #12

Open
cipriancraciun opened this issue May 27, 2013 · 3 comments
Open

[feature-request] Adding a few new formatting options #12

cipriancraciun opened this issue May 27, 2013 · 3 comments

Comments

@cipriancraciun
Copy link

(All these options can be implemented independently.)

A new option (like say %P, from "pointer"), that in case of symlinks or hardlinks it outputs only the pointed path. (Thus complementing the %n / %N in this case.) (high priority)

An option to print the inode number (say %I) (and possibly the containing device number, say %D), used for example to detect renames.

@miekg
Copy link
Owner

miekg commented May 27, 2013

[ Quoting [email protected] in "[rdup] [feature-request] Adding a f..." ]

(All these options can be implemented independently.)

A new option (like say %P, from "pointer"), that in case of symlinks or hardlinks it outputs only the pointed path. (Thus complementing the %n / %N in this case.) (high priority)

What do you mean with high priority? (I do accept patches :) ), You can
also split the strings on ' -> ' when rdup outputs a 'l' or 'h' line.

An option to print the inode number (say %I) (and possibly the containing device number, say %D), used for example to detect renames.

Those are relative easy additions, but rdup should have detected these
renames already (there is a '-' line and a '+' for these renames)

  • Grtz,


    Miek Gieben

@cipriancraciun
Copy link
Author

:) By "high priority" I meant "if it happens that you have time to choose any of these, I would suggest this one". It wasn't my intention to imply any "requirement". :) (I do understand how open-source works.)

About line splitting: I've done exactly that, i.e. sed after ->, however as I use a custom format string, I would have preferred using tab or something else, because -> might easily appear in a file name...

About the other inode option, I currently use (actually experiment with) rdup as a way to collect meta-data of a file-system and include it with besides the data itself, thus I always invoke it for a full backup. (Imagine putting all the files on a plain ISO stripped of any POSIX meta-data, with a .rdup file in the root that serves both to store meta-data and sums; or inside a ZIP file, or in S3, etc.)

@miekg
Copy link
Owner

miekg commented May 27, 2013

Ah OK. Sounds like a very reasonable request.
On 27 May 2013 16:01, "Ciprian Dorin Craciun" [email protected]
wrote:

:) By "high priority" I meant "if it happens that you have time to choose
any of these, I would suggest this one". It wasn't my intention to imply
any "requirement". :) (I do understand how open-source works.)

About line splitting: I've done exactly that, i.e. sed after ->, however
as I use a custom format string, I would have preferred using tab or
something else, because -> might easily appear in a file name...

About the other inode option, I currently use (actually experiment with)
rdup as a way to collect meta-data of a file-system and include it with
besides the data itself, thus I always invoke it for a full backup.
(Imagine putting all the files on a plain ISO stripped of any POSIX
meta-data, with a .rdup file in the root that serves both to store
meta-data and sums; or inside a ZIP file, or in S3, etc.)


Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-18502648
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants