You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.
As I pointed out in the root ipfs/kubo#1195 message, a useful extention for the UI would be a repeatable --ignore <ip*s-path> argument to the export command which would allow to to say “export all objects reachable by <names-listed-in-the-positional-arguments>except for <names-listed-in-ignore-options> and their descendents”. That's the same sort of thing you can do with:
$ git bundle create mybundle v1.0.0..master
for “bundle all objects reachable from my master branch reference except for those reachable from my v1.0.0 tag”, but I like the separate option to make it easier to truncate in multiple locations.
I'm pretty confident that that's a good UI, but I'm not sure how we want to represent these instances in the archive file. Constraints:
We want this to be unambiguous (obviously).
We want a fast way to get the list of ignored IP*S paths, so a node can quickly check whether or not it already has the ignored IPFS objects locally. Nodes may want to check that they can resolve any non-IPFS links (e.g. dnslinks, IPNS links, …).
That sounds like a separate header table listing the ignored <ip*s-paths>. Or maybe just a magic 0 offset in the main index (but that's going to be hard to distinguish if we don't store the full multihash in that lookup table)? I'll try to find specs for how Git's bundle handles this situation without looking through any GPLed code.
The text was updated successfully, but these errors were encountered:
As I pointed out in the root ipfs/kubo#1195 message, a useful extention for the UI would be a repeatable
--ignore <ip*s-path>
argument to the export command which would allow to to say “export all objects reachable by<names-listed-in-the-positional-arguments>
except for<names-listed-in-ignore-options>
and their descendents”. That's the same sort of thing you can do with:for “bundle all objects reachable from my master branch reference except for those reachable from my v1.0.0 tag”, but I like the separate option to make it easier to truncate in multiple locations.
I'm pretty confident that that's a good UI, but I'm not sure how we want to represent these instances in the archive file. Constraints:
That sounds like a separate header table listing the ignored
<ip*s-paths>
. Or maybe just a magic 0 offset in the main index (but that's going to be hard to distinguish if we don't store the full multihash in that lookup table)? I'll try to find specs for how Git's bundle handles this situation without looking through any GPLed code.The text was updated successfully, but these errors were encountered: