Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
20 check-ins using file src/deltacmd.c version 264cce36be
|
2011-10-20
| ||
| 02:03 | Sorry, wrong branch! started changelog for 1.20 release. ... (Closed-Leaf check-in: a942086390 user: stephan tags: declined) | |
|
2011-10-15
| ||
| 00:10 | The link <strong>p</strong> in the annotate page was totally bad implemented. As I don't see an easy way to implement it, I take it out. There is only <strong>d</strong> left. ... (check-in: 4bae75a08e user: viriketo tags: annotate_links) | |
| 00:06 | The plink is not needed at all in the annotate query ... (check-in: 40cbb69c4f user: viriketo tags: annotate_links) | |
|
2011-10-14
| ||
| 23:38 | Starting a branch to add more information into the annotate web page. I added a link <strong>p</strong> to the annotation of the version previous to that line change, and a link <strong>d</strong> to the checkin file diff that introduced the given line. I'd want also the links to bring the users to the concerning line of annotate; we should have something like line numbering and line anchors, like the artifact page. ... (check-in: 9e3b6ad052 user: viriketo tags: annotate_links) | |
| 22:20 | Making 'fossil merge' also report a conflict for extra files overwritten. Like [60c6197c8a], but for the merge operation. Related to ticket [953031915f]. ... (check-in: bb49278a8a user: viriketo tags: declined) | |
| 22:16 | Reporting the number of merge conflicts at the end of merge, as with update. I think the information is of value to the user. I think that had to be introduced in [070ce24d838a6], from its comment, but that change made the opposite of commented. ... (check-in: e1a7a1d9e2 user: viriketo tags: declined) | |
| 20:25 | Making fossil warn about a conflict, if an update operation overwrites an extra file. This should close ticket [953031915f]. ... (check-in: 60c6197c8a user: viriketo tags: declined) | |
| 19:53 | Same trouble as [bf480a29a6] but for the merge5 test. ... (check-in: 129605856a user: viriketo tags: declined) | |
| 19:46 | Fixing the merge5 test, for it to run when out of a checkout. The same kind of fix as [0a7ab3ccb0]. ... (check-in: e46be99ff4 user: viriketo tags: declined) | |
| 19:01 | Fixing the merge_renames test; fossil was using $HOME somehow. I noticed it running the test in an environment without a valid $HOME path (the nix package building). fossil refused to run the 'fossil new' inside the merge_renames test. ... (check-in: bf480a29a6 user: viriketo tags: declined) | |
| 16:12 | Merging the extended_ci_names branch, that introduces more ways of naming checkins in diff and update operations. ... (check-in: 107e605f41 user: viriketo tags: declined) | |
| 16:11 | Merging the annotate_noleak changes, about removing an important memory leak in the annotate operation. It also fixes some blob behaviour in blob.c and content.c. <b>Update:</b> Removed from trunk. Replaced by the must simpler fix at [9929bab702f99839ee] ... (check-in: 409f370a6d user: viriketo tags: declined) | |
|
2011-09-13
| ||
| 17:18 | The Label list was not properly freed in some cases; looking at the annotate of 'win/Makefile.msc' was triggering the case. ... (Closed-Leaf check-in: 4860d9f234 user: viriketo tags: annotate_noleak) | |
| 16:43 | Getting in the changes reducing the leak on annotate. In the fossil mailing list, I received only opinions in favour of getting mallocs and frees properly paired, so I think noone will refuse the change. ... (check-in: 7870a89b10 user: viriketo tags: annotate_noleak) | |
|
2011-09-06
| ||
| 20:30 | Documenting the Label structure I introduced. ... (Closed-Leaf check-in: 58a02a2e4a user: viriketo tags: label_linkedlist) | |
|
2011-09-04
| ||
| 22:14 | Implementation of a linked list to solve the memory leak described in a TODO in [e2ebb1f5cae8]. This code is slower than having the memory leak, and at the end, it was not a big memory leak. Let's say, 10 byte per revision involved in a file annotate. If a file has 30000 revisions, it may go around 300KB then. For this leak to be noticeable (as we have a content cache until 50MB), it would mean having above a milion revisions for the file annotated. So, I keep this in a branch apart, as maybe the leak is worth the faster code. I have not measured the speed difference though. ... (check-in: ef8266b710 user: viriketo tags: label_linkedlist) | |
| 21:39 | Reducing the leak of annotate even more. I wrote a TODO in the file, for a leak still present and relevant for files modified by many versions, but that requires harder work to get right. ... (check-in: e2ebb1f5ca user: viriketo tags: annotate_noleak) | |
| 21:02 | Making annotate not segfault for the complex test case I have. There is still a little leak... but muuuch smaller than it was. ... (check-in: fa760a24cd user: viriketo tags: annotate_noleak) | |
| 20:43 | Updating from trunk to get the latest code. ... (check-in: 73b6ff4966 user: viriketo tags: annotate_noleak) | |
| 20:41 | What I did to get the 'annotate' command not leak. Notice that I disabled again the check for blob_is_reset, as in trunk. ... (check-in: 7ad4dfbe8b user: viriketo tags: annotate_noleak) | |