Re: [fossil-users] Cutting fossil repository
I sent two examples and asked whether they were correct. A simple "yes" or "no" would be enough... 1) Is the following correct? fossil purge artifacts 86848307235407 2) can I delete several commits like this? fossil purge artifacts 86848307235407 563453457234 56488921223 Thanks. On Sat, 2016-10-08 at 18:40 -0400, Richard Hipp wrote: > On 10/8/16, Adam Jensen wrote: > > > > The reluctance of some programmer communities to provide examples has > > always surprised me. > > In this case, the documentation > (https://www.fossil-scm.org/fossil/help?cmd=purge) consists of a > series of examples, each followed by an explanation of what that > example does. > > I do not know how to make the documentation any clearer. > Contributions from others who do know how to make better documentation > will be greatly appreciated. > ___ 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] Cutting fossil repository
1) But what about the first case? Is the following correct: fossil purge artifacts 86848307235407 2) can I delete several commits like this: fossil purge artifacts 86848307235407 563453457234 56488921223 Thanks. On Sat, 2016-10-08 at 14:58 -0400, Richard Hipp wrote: > On 10/8/16, Zeev Pekar wrote: > > > > 2) using shun: > > > > fossil shun 86848307235407 (this is just a guess since this one I > > couldn't find in docs) > > > > Am I right? > > There is no "shun" command. Shunning must be done from the web interface. ___ 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] Cutting fossil repository
Ok, so let me try... Let's say we want to delete a commit 86848307235407 1) using purge it should be: fossil purge artifacts 86848307235407 2) using shun: fossil shun 86848307235407 (this is just a guess since this one I couldn't find in docs) Am I right? Thank you. On Sat, 2016-10-08 at 14:28 -0400, Richard Hipp wrote: > On 10/8/16, Zeev Pekar wrote: > > Ok. I understood the consequences - I'll operate on a copy of a repo. So > > could you, please, provide the two examples anyway? > > > > I do not know how to improve upon > https://www.fossil-scm.org/fossil/help?cmd=purge > > If you can explain what part of the documentation is unclear, perhaps > we can clarify it for you. > ___ 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] Cutting fossil repository
Ok. I understood the consequences - I'll operate on a copy of a repo. So could you, please, provide the two examples anyway? Thank you. On Sat, 2016-10-08 at 14:19 -0400, Richard Hipp wrote: > On 10/8/16, Zeev Pekar wrote: > > Could somebody, please, provide an example of deleting a commit, using > > a) purge > > b) shun > > > > If you need an example in order to pull this off, then it is not > something you should attempt. The use of purge and shun is for > experts only. If you do not have a full understanding of what you are > doing, you will likely end up making a mess. > > Fossil is designed to never forget things. You are asking it to > forget, which goes against its very nature. Some provisions are made > for this, for exceptional circumstances. But those provisions are > very seldom used, and are not novice-friendly. > > ___ 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] Cutting fossil repository
Could somebody, please, provide an example of deleting a commit, using a) purge b) shun Thank you in advance! Zeev On Fri, 2016-10-07 at 15:57 -0400, Richard Hipp wrote: > 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 sync from another > repo that holds them. > > I think. Double-check before relying on what I said above. :-) > > > 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://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Cutting fossil repository
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 commits (which were made later than the required date) by hand, one by one? if yes - how? Thank you in advance, Zeev ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Using fossil as CMS
Hi, I'm considering droping Drupal and move to using fossil also as a CMS. 1) How difficult is it to port a Drupal theme to fossil? I have a nivo slider ( http://nivo.dev7studios.com/ ) on my homepage - will it work in fossil? Does fossil have following features, and if not, what are the chances that they will be implemented in some near future? 2) Does fossil index wiki pages, so that one can search all existing documents for a specific string? 3) Are there forms to contact developers/admin without exposing their emails? Thank you, Zeev ___ 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] 2 questions
- Original message - > On Fri, Nov 4, 2011 at 12:25 PM, Zeev Pekar wrote: > > > ** > > > > I do miss this feature... :( What is the best workaround for this > > today? > > > > To use a DVCS which supports this. i'm not personally aware of any. > gitolite supports ACL on paths if I'm not mistaken... > > > To developers: do you think this is important enough for you to > > implement it one day? > > > > It would be impossible to implement within fossil's world view. Once i > clone a repo i have the whole thing, which i can then manipulate (with > admin-level rights) on my machine - you cannot stop me from checking out > a given path once i have access to a clone of the repo. There is no > mechanism with which fossil can completely protect subdirectories unless > it explicitly supports "partial clones" (pulling only part of the repo). Ok, maybe implement "partial clones"? ___ 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] 2 questions
> > 2) is it possible to deny access to folders of the source tree to > > certain users and grant access to the rest of the folders? (like in > > gitolite) > > There is no ACL on path names. I do miss this feature... :( What is the best workaround for this today? To developers: do you think this is important enough for you to implement it one day? > > > ps: I've asked Anjuta developers to create a fossil plug-in and they > > agreed :) > > https://bugzilla.gnome.org/show_bug.cgi?id=663313 > > Nice! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] 2 questions
Hi, I have 2 questions regarding fossil: 1) if I have 2 projects do I have to a) create 2 separate repositories or do I b) put both source trees in one repository? if a), how do I run fossil server to make both repositories accessible at the same time from outside? 2) is it possible to deny access to folders of the source tree to certain users and grant access to the rest of the folders? (like in gitolite) thank you Zeev ps: I've asked Anjuta developers to create a fossil plug-in and they agreed :) https://bugzilla.gnome.org/show_bug.cgi?id=663313 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
