Re: [fossil-users] forget binary files
On Thu, Aug 6, 2015 at 8:26 AM, Luca Ferrari fluca1...@infinito.it wrote: I suspect the answer will be NO, Correct. but any chance I can export only a subtree of the repository (along with its history) and import into a new repositorym so to avoid having binaries? Or any chance to force sqlite to forget about such binaries? nope - the binaries are referenced in so-called manifests (formal change records of any repo content), and removing them affects not only those checkins, but all checkins which subsequently derive (even indirectly) from them. A change of a checkin changes its hash, invalidating anything which points to its old hash. Fossil intentionally makes it _very_ difficult (effectively impossible) to change the past. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Wed, Aug 5, 2015 at 4:52 PM, Andy Goth andrew.m.g...@gmail.com wrote: On 8/4/2015 6:06 AM, Stephan Beal wrote: On Tue, Aug 4, 2015 at 1:02 PM, David Mason dma...@ryerson.ca mailto:dma...@ryerson.ca wrote: Just be careful not to shun 0 length files or you won't be able to commit a 0-length file until you've cleared the shun table (because all 0-length files have the same SHA-1 id. Excellent point, though it's hard to imagine such files being either binary or holding sensitive data (except maybe in their name... hmmm interesting corner case). Files (rather, artifacts) are not shunned by name but by contents. If a file's name is the problem, shun the manifest containing the name. I suspect the answer will be NO, but any chance I can export only a subtree of the repository (along with its history) and import into a new repositorym so to avoid having binaries? Or any chance to force sqlite to forget about such binaries? Please note: it's fine for me to keep the repo as it is, after all it was my mistake, but I would like to fix it without loosing all the history. Luca ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On 8/4/2015 6:06 AM, Stephan Beal wrote: On Tue, Aug 4, 2015 at 1:02 PM, David Mason dma...@ryerson.ca mailto:dma...@ryerson.ca wrote: Just be careful not to shun 0 length files or you won't be able to commit a 0-length file until you've cleared the shun table (because all 0-length files have the same SHA-1 id. Excellent point, though it's hard to imagine such files being either binary or holding sensitive data (except maybe in their name... hmmm interesting corner case). Files (rather, artifacts) are not shunned by name but by contents. If a file's name is the problem, shun the manifest containing the name. -- Andy Goth | andrew.m.goth/at/gmail/dot/com signature.asc Description: OpenPGP digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On 4 August 2015 at 06:09, Stephan Beal sgb...@googlemail.com wrote: On Tue, Aug 4, 2015 at 12:04 PM, Luca Ferrari fluca1...@infinito.it wrote: On Tue, Aug 4, 2015 at 11:31 AM, Stephan Beal sgb...@googlemail.com wrote: http://www.fossil-scm.org/index.html/help?cmd=/shun In that case you would have to shun all of the files individually. Fossil, by design, makes it exceedingly difficult to change history, and that includes removing files. Shunning is really only intended to be used when someone checks in sensitive or malicious data. But it's a reasonable way to remove binaries that you don't want. Just be careful not to shun 0 length files or you won't be able to commit a 0-length file until you've cleared the shun table (because all 0-length files have the same SHA-1 id. ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, Aug 4, 2015 at 1:02 PM, David Mason dma...@ryerson.ca wrote: But it's a reasonable way to remove binaries that you don't want. Indeed - my point was only that shunning as a feature is _primarily_ intended as a way to remove sensitive or malicious stuff. Just be careful not to shun 0 length files or you won't be able to commit a 0-length file until you've cleared the shun table (because all 0-length files have the same SHA-1 id. Excellent point, though it's hard to imagine such files being either binary or holding sensitive data (except maybe in their name... hmmm interesting corner case). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, Aug 4, 2015 at 1:47 PM, Sergei Gavrikov sergei.gavri...@gmail.com wrote: I know one, that's 'The Infinitely Profitable Program' http://peetm.com/blog/?p=55 :-) To summarize: GO.COM contained no program bytes at all – it was entirely empty. However, because GO.COM was empty, but still a valid program file as far as CP/M was concerned (it had a directory entry and file-name ending with .com), the CP/M loader, the part of the OS whose job it is to pull programs off disk and slap them into the TPA, would still load it! Wow. i like to think that wouldn't be possible today. But, who knows... it's potentially possible to encode a whole virus in a long filename of an empty file, sharing the same hash as all other empty files. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, Aug 4, 2015 at 12:04 PM, Luca Ferrari fluca1...@infinito.it wrote: On Tue, Aug 4, 2015 at 11:31 AM, Stephan Beal sgb...@googlemail.com wrote: http://www.fossil-scm.org/index.html/help?cmd=/shun shunning is the only way to remove something and should be considered a last resort option. Thanks, but not quite what I was searching for: I need to remove a full tree of files, so I don't have an exact SHA artifact, if I get it right. In that case you would have to shun all of the files individually. Fossil, by design, makes it exceedingly difficult to change history, and that includes removing files. Shunning is really only intended to be used when someone checks in sensitive or malicious data. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, 4 Aug 2015, Stephan Beal wrote: On Tue, Aug 4, 2015 at 1:02 PM, David Mason dma...@ryerson.ca wrote: Just be careful not to shun 0 length files or you won't be able to commit a 0-length file until you've cleared the shun table (because all 0-length files have the same SHA-1 id. Excellent point, though it's hard to imagine such files being either binary or holding sensitive data (except maybe in their name... hmmm interesting corner case). I know one, that's 'The Infinitely Profitable Program' http://peetm.com/blog/?p=55 :-) Sergei___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, 4 Aug 2015, Stephan Beal wrote:
On Tue, Aug 4, 2015 at 1:47 PM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
I know one, that's 'The Infinitely Profitable Program'
http://peetm.com/blog/?p=55 :-)
To summarize:
GO.COM contained no program bytes at all – it was entirely empty. However,
because GO.COM was empty, but still a valid program file as far as CP/M was
concerned (it had a directory entry and file-name ending with .com), the CP/M
loader, the part of the OS whose job it is to pull programs off disk and slap
them into the TPA, would still load it!
Wow. i like to think that wouldn't be possible today. But, who
knows... it's potentially possible to encode a whole virus in a long
filename of an empty file, sharing the same hash as all other empty
files.
[OFF-TOPIC]
I used GO.COM recently on one modern LEON3 target in self cooked
boot-loader. I used XMODEM to upload binary files and I looked for a way
to run application and return to the loader and return back (quickly) to
loaded application again. From my local web-log (jemdoc mark-down):
== 2015\/01\/12
Implement +Th_Eval2()+. In first, +Th_Eval2()+ does try to find a dot-com file
on CFS.
=== GO.COM
- [http://peetm.com/blog/?p=55]
It works!
~~~
{}{}
0 qm ls
hello.tcl init GO.COM HELLO.COM
0 qm HELLO
HELLO, WORLD!
0 qm GO
HELLO, WORLD!
~~~
BTW, +GO.COM+ was created as
~~~
{}{}
0 qm write GO.COM
~~~
Well, my COMMAND.COM on the target was TH1 interpreter :-)
Sergei___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, Aug 4, 2015 at 11:31 AM, Stephan Beal sgb...@googlemail.com wrote: http://www.fossil-scm.org/index.html/help?cmd=/shun shunning is the only way to remove something and should be considered a last resort option. Thanks, but not quite what I was searching for: I need to remove a full tree of files, so I don't have an exact SHA artifact, if I get it right. out of curiosity: did the binaries get added via the 'addremove' command? No, it was mistakenly added in a previous repo and then here. Luca ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] forget binary files
On Tue, Aug 4, 2015 at 11:22 AM, Luca Ferrari fluca1...@infinito.it wrote: Hi, this may sound stupid, but once I've mistakenly committed binary files, is there a way to remove them from the repository at all? My attempt is (i) to not version such files and (ii) reduce repository size. see: http://www.fossil-scm.org/index.html/help?cmd=/shun shunning is the only way to remove something and should be considered a last resort option. out of curiosity: did the binaries get added via the 'addremove' command? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
