On 10/7/16, sky5w...@gmail.com wrote:
> Cool.
> How does 'fossil purge obliterate' differ from 'fossil shun'?
"shun" rmembers the SHA1 hash and will never again accept that SHA1
hash on a sync. "fossil purge whatever" simply deletes the artifacts
from the local repo. They will be restored on a
Cool.
How does 'fossil purge obliterate' differ from 'fossil shun'?
Is shun obsoleted or superseded by purge now?
Can I achieve the obliteration entirely from the cmd line?
Thanks!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://li
Maybe you could make a copy of the repo then "purge" all those
check-ins and files you don't want from the copy:
https://www.fossil-scm.org/fossil/help?cmd=purge
On 10/7/16, Zeev Pekar wrote:
> Hello,
>
> if one needs to provide a partial repo (from the beginning till certain
> date/commit) to a
On Fri, Oct 7, 2016 at 9:20 AM, Zeev Pekar wrote:
> Hello,
>
> if one needs to provide a partial repo (from the beginning till certain
> date/commit) to a third party - how should he generate this new partial
> repo from the existing full one?
>
> 1) is there a way to "cut" a repo till certain da
Hello,
if one needs to provide a partial repo (from the beginning till certain
date/commit) to a third party - how should he generate this new partial
repo from the existing full one?
1) is there a way to "cut" a repo till certain date/commit? if yes -
how?
2) is it possible to delete all the co
5 matches
Mail list logo