Re: [fossil-users] Fossil destroys repositories?
On Tue, Jul 26, 2011 at 8:56 PM, Eric e...@deptj.eu wrote: As I understand it, the repository was never destroyed at all, and uncommitted chages were destroyed by a fossil revert which does exactly that by design. I think it is worth mentioning you can undo a revert - but only if you do so immediately. (I think this is now in the command line documentation.) Is revert like 'shun' in that it permanently removes artifacts from the repository? Stephen ___ 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] Fossil destroys repositories?
On Jul 27, 2011, at 15:22 , Stephen De Gabrielle wrote: Is revert like 'shun' in that it permanently removes artifacts from the repository? It works on local copy, not the repository. So it deals with on-disk files, not artifacts. Kind regards, Remigiusz Modrzejewski ___ 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] Fossil destroys repositories?
On Wed, Jul 27, 2011 at 9:22 AM, Stephen De Gabrielle stephen.degabrie...@acm.org wrote: Is revert like 'shun' in that it permanently removes artifacts from the repository? Stephen I understood revert to revert things like merges and local changes, rather than affecting the repository itself. Wes ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Anonymous no longer allowed to create new tickets
To report bugs or ask for enhancements in Fossil, please post to this mailing list. Because of noise and test tickets (which by the nature of fossil are permanent) the ability for anonymous users to create new tickets has been disabled. If you have an issue, report it here, and one of the many users with logins will write a new ticket for you, if that is an appropriate thing to do. We have previously implemented a similar policy at SQLite and that seems to be working well. There really needs to be a filter on ticket creation to weed out the (considerable) noise. Perhaps we can figure out a design change in Fossil that makes tickets anonymously-created ephemeral until approved by a registered user -- D. Richard Hipp d...@sqlite.org ___ 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] Anonymous no longer allowed to create new tickets
We have previously implemented a similar policy at SQLite and that seems to be working well. There really needs to be a filter on ticket creation to weed out the (considerable) noise. Perhaps we can figure out a design change in Fossil that makes tickets anonymously-created ephemeral until approved by a registered user I think this is already possible with some fancy Ticket form action and SQLite filtering. Couldn't you just use the default status drop down, and say there is a Submitted one that anonymous users submit to, and then a registered user can move it to Accepted , and the default report for tickets makes sure only those that are Accepted are the ones that the devs care about and try to fix. I actually thought that this was what the status dropdown was for when I first downloaded fossil. Since I just use it for my own projects, I deleted the other options. Tomek ___ 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] Anonymous no longer allowed to create new tickets
On Jul 27, 2011, at 22:06 , Richard Hipp wrote: To report bugs or ask for enhancements in Fossil, please post to this mailing list. Because of noise and test tickets (which by the nature of fossil are permanent) the ability for anonymous users to create new tickets has been disabled. If you have an issue, report it here, and one of the many users with logins will write a new ticket for you, if that is an appropriate thing to do. Good. We should also do something with the noise already in the system. I can contribute a modest amount of time to that end. We have previously implemented a similar policy at SQLite and that seems to be working well. There really needs to be a filter on ticket creation to weed out the (considerable) noise. Perhaps we can figure out a design change in Fossil that makes tickets anonymously-created ephemeral until approved by a registered user Better. But I'm still unhappy with the concept of anonymous participation per se (up to the point that I contributed self-register, which unfortunately is largely ignored). Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Editing commit dates
Hi, Some help / pointers here will be useful I looked at timeline (UI) of one of my projects today and found a commit with a future date, resulting in an N shape in timeline graph. I tried updating the commit date using web interface but the graph did not change. Looking at the commit information again, it says following under Overview: Date: 5695-09-30 21:53:28 Received From: a0756885 @ on 5695-09-30 21:53:28 However, it says following under Tags and Properties: date=2010-06-23 16:53:28 added by [7396a17ae0] on 5695-09-30 22:06:36 It looks like I already tried to fix it in past. Any attempt to change the commit date (I tried changing it to 2010-06-24 21:53:28 using 'edit' link) does not take effect and commit information always shows above values. When I click [7396a17ae0] link, I get: Control artifact. D 5695-09-30T22:06:36 T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 U a0756885 Z 78cd9d21c70bd742573d4c09577cc20d I did fossil rebuild and changing date again through web interface with fossil version 1.18 [df9da91ba8], but it did not help. Is there a limit on how many times a commit date can be edited? How do I fix this one? I did deconstruct in a temp folder and searched for files containing +date, which shows many files, relating to various attempts I made to correct it: $ grep -R +date * 1d/31959a78f56dfab7f7008c409e306e50c548fe:T +date 2c585f0435a3cb128032442d6bd7ff75dfad3864 2010-01-07\s04:48:16 1d/cc744d2aa2a46567721bd9e03db07d5aef7fba:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 5c/011a1e3ac40f570c05f21a23ac07f0cd4015f1:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 6b/46affaa42c5014baf8a96ae82d592e9f82e347:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 73/96a17ae080a920f9287544f0e48472488bbbc8:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 8c/ab10e029c16fb93283c3849e06552276a2:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 a9/bb299a9e185f8532ebf12fe7664bb12eac4112:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s21:53:28 d8/84e3ccb48e5e214ab28592a86b077d5c0a5052:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2012-09-30\s21:53:28New repository after reconstruct shows same issue. - Altu ___ 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] Editing commit dates
What is I deconstruct, delete all files having +date records and then reconstruct? Will that be safe? - Original Message - From: Altu Faltu Sent: 07/28/11 07:51 AM To: fossil users Subject: [fossil-users] Editing commit dates Hi, Some help / pointers here will be useful I looked at timeline (UI) of one of my projects today and found a commit with a future date, resulting in an N shape in timeline graph. I tried updating the commit date using web interface but the graph did not change. Looking at the commit information again, it says following under Overview: Date: 5695-09-30 21:53:28 Received From: a0756885 @ on 5695-09-30 21:53:28 However, it says following under Tags and Properties: date=2010-06-23 16:53:28 added by [7396a17ae0] on 5695-09-30 22:06:36 It looks like I already tried to fix it in past. Any attempt to change the commit date (I tried changing it to 2010-06-24 21:53:28 using 'edit' link) does not take effect and commit information always shows above values. When I click [7396a17ae0] link, I get: Control artifact. D 5695-09-30T22:06:36 T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 U a0756885 Z 78cd9d21c70bd742573d4c09577cc20d I did fossil rebuild and changing date again through web interface with fossil version 1.18 [df9da91ba8], but it did not help. Is there a limit on how many times a commit date can be edited? How do I fix this one? I did deconstruct in a temp folder and searched for files containing +date, which shows many files, relating to various attempts I made to correct it: $ grep -R +date * 1d/31959a78f56dfab7f7008c409e306e50c548fe:T +date 2c585f0435a3cb128032442d6bd7ff75dfad3864 2010-01-07\s04:48:16 1d/cc744d2aa2a46567721bd9e03db07d5aef7fba:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 5c/011a1e3ac40f570c05f21a23ac07f0cd4015f1:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 6b/46affaa42c5014baf8a96ae82d592e9f82e347:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 73/96a17ae080a920f9287544f0e48472488bbbc8:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 8c/ab10e029c16fb93283c3849e06552276a2:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 a9/bb299a9e185f8532ebf12fe7664bb12eac4112:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s21:53:28 d8/84e3ccb48e5e214ab28592a86b077d5c0a5052:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2012-09-30\s21:53:28New repository after reconstruct shows same issue. - Altu ___ 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] Editing commit dates
On Wed, Jul 27, 2011 at 10:21 PM, Altu Faltu altufa...@mail.com wrote: Hi, Some help / pointers here will be useful I looked at timeline (UI) of one of my projects today and found a commit with a future date, resulting in an N shape in timeline graph. I tried updating the commit date using web interface but the graph did not change. Looking at the commit information again, it says following under Overview: Date: 5695-09-30 21:53:28 Received From: a0756885 @ on 5695-09-30 21:53:28 This date can be corrected. But the rule is, the oldest record wins. So the edit that fixes this date must occur after 5695-09-30. It is clearly impractical to wait that long. But at this point in time, there is not a easy way that I know of to override the date for an edit record. I'll have to work on that. How badly is your system clock broken in order to get such a date? However, it says following under Tags and Properties: date=2010-06-23 16:53:28 added by [7396a17ae0] on 5695-09-30 22:06:36 It looks like I already tried to fix it in past. Any attempt to change the commit date (I tried changing it to 2010-06-24 21:53:28 using 'edit' link) does not take effect and commit information always shows above values. When I click [7396a17ae0] link, I get: Control artifact. D 5695-09-30T22:06:36 T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 U a0756885 Z 78cd9d21c70bd742573d4c09577cc20d I did fossil rebuild and changing date again through web interface with fossil version 1.18 [df9da91ba8], but it did not help. Is there a limit on how many times a commit date can be edited? How do I fix this one? I did deconstruct in a temp folder and searched for files containing +date, which shows many files, relating to various attempts I made to correct it: $ grep -R +date * 1d/31959a78f56dfab7f7008c409e306e50c548fe:T +date 2c585f0435a3cb128032442d6bd7ff75dfad3864 2010-01-07\s04:48:16 1d/cc744d2aa2a46567721bd9e03db07d5aef7fba:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 5c/011a1e3ac40f570c05f21a23ac07f0cd4015f1:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 6b/46affaa42c5014baf8a96ae82d592e9f82e347:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 73/96a17ae080a920f9287544f0e48472488bbbc8:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 8c/ab10e029c16fb93283c3849e06552276a2:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 a9/bb299a9e185f8532ebf12fe7664bb12eac4112:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s21:53:28 d8/84e3ccb48e5e214ab28592a86b077d5c0a5052:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2012-09-30\s21:53:28 New repository after reconstruct shows same issue. - Altu ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
