ostree

Commit Graph

Author	SHA1	Message	Date
Colin Walters	688d8f176b	pull: Always scan for commit object, even if ref is unchanged If the admin encounters corruption and does: $ ostree admin fsck --delete We want them to be able to recover the objects easily from the network; with this patch, they do: $ ln -s dummyvalue /ostree/repo/transaction $ ostree refs --delete remotename:branchname $ ostree pull remotename This patch avoids the need for the refs --delete; we might as well force scan the commit, and with this patch we still print that it changed.	2013-07-23 19:36:15 -04:00
Colin Walters	ea914e7e49	main: pull: Reduce the status line length a bit Drop "objects" where it's obvious [ to me anyways =) ], and drop the bytes transferred since our math was off, and the HTTP status kind of shows that.	2013-07-23 17:29:46 -04:00
Colin Walters	2535f32c56	libostree: Move pull code into here More library work.	2013-07-09 20:14:53 -04:00

Author

SHA1

Message

Date

Colin Walters

688d8f176b

pull: Always scan for commit object, even if ref is unchanged

If the admin encounters corruption and does:

$ ostree admin fsck --delete

We want them to be able to recover the objects easily from the
network; with this patch, they do:

$ ln -s dummyvalue /ostree/repo/transaction
$ ostree refs --delete remotename:branchname
$ ostree pull remotename

This patch avoids the need for the refs --delete; we might as well
force scan the commit, and with this patch we still print that it
changed.

2013-07-23 19:36:15 -04:00

Colin Walters

ea914e7e49

main: pull: Reduce the status line length a bit

Drop "objects" where it's obvious [ to me anyways =) ], and drop the
bytes transferred since our math was off, and the HTTP status kind of
shows that.

2013-07-23 17:29:46 -04:00

Colin Walters

2535f32c56

libostree: Move pull code into here

More library work.

2013-07-09 20:14:53 -04:00

1 2 3 4

153 Commits