Fri, 09 Jul 2021 06:47:09 +0100 Fix (bad) source corruption when committing private classes
Jan Vrany <jan.vrany@labware.com> [Fri, 09 Jul 2021 06:47:09 +0100] rev 928
Fix (bad) source corruption when committing private classes This commit fixes a really bad bug causing source corruption when committing private classes *and* when using original repository for commits ( `hgUseOriginalRepositories: true`). This was becase private classes's source was not made local prior opening the enclosing class's container for writing! Sigh.
Fri, 19 Feb 2021 12:14:01 +0100 Converting the windows style path (with '\') into unix one ('/'). The filenames at HGCommandParser>>parseCommandLocate changed the path style on Windows.
Patrik Svestka <patrik.svestka@gmail.com> [Fri, 19 Feb 2021 12:14:01 +0100] rev 927
Converting the windows style path (with '\') into unix one ('/'). The filenames at HGCommandParser>>parseCommandLocate changed the path style on Windows.
Tue, 01 Jun 2021 12:30:12 +0100 Fix `HGContribution class >> initialize`
Jan Vrany <jan.vrany@labware.com> [Tue, 01 Jun 2021 12:30:12 +0100] rev 926
Fix `HGContribution class >> initialize` Recent `Timestamp` parser is more strict and does parse when only date is given. Makes sense.
Thu, 08 Oct 2020 14:04:07 +0100 Add (experimental) option to use original working copy for commits
Jan Vrany <jan.vrany@labware.com> [Thu, 08 Oct 2020 14:04:07 +0100] rev 925
Add (experimental) option to use original working copy for commits ...rather than (possibly shared) temporary one. Use of temporary one makes a lot of things more complex and error-prone (such as, amending commits and handling bookmarks). Moreover, it is confusing for most users and hard to understand what has happened when something goes wrong. This should make things simpler and more like things work in non-Smalltalk world.
Fri, 19 Feb 2021 08:29:41 +0000 Rework and fix HGSourceCodeManager >> #revisionLogOf:...directory:module:`
Jan Vrany <jan.vrany@labware.com> [Fri, 19 Feb 2021 08:29:41 +0000] rev 924
Rework and fix HGSourceCodeManager >> #revisionLogOf:...directory:module:` This commit changes the logic in two ways: 1. #newestRevision is now the newest revision in the branch that *contains* given file (not necesarily modidfes it). If there are multiple heads in that branch, pretty much random one is returned. This changes old behavior and therefore this commit updates tests. 2. If a specific single revision is requested, i.e., both from and to revisions are the same, revision log with that single revision is returned no matter whether it modifies the file or even contains that file at all. This is essentially a workaround to fix issue #305. Moreover, this commit simplifies the code a lot by delegating all the changeset searching and filtering to mercurial using revset expressions. See https://swing.fit.cvut.cz/projects/stx-jv/ticket/305#comment:3
Wed, 17 Feb 2021 15:01:13 +0000 Fix issue with bookmark not advancing upon commit
Jan Vrany <jan.vrany@labware.com> [Wed, 17 Feb 2021 15:01:13 +0000] rev 923
Fix issue with bookmark not advancing upon commit ...when original repository is used. This was caused by forcefull updating of working copy to a revision, which deactivates active bookmark.
Tue, 16 Feb 2021 08:42:02 +0000 Add tests checking that bookmark is moved upon commit
Jan Vrany <jan.vrany@labware.com> [Tue, 16 Feb 2021 08:42:02 +0000] rev 922
Add tests checking that bookmark is moved upon commit
Fri, 29 Jan 2021 08:53:32 +0000 Fix "slow grow operation" warning when commiting extensions only
Jan Vrany <jan.vrany@labware.com> [Fri, 29 Jan 2021 08:53:32 +0000] rev 921
Fix "slow grow operation" warning when commiting extensions only While harmless, it's bit distracting. Better fixed.
Fri, 29 Jan 2021 08:49:31 +0000 Fix nasty bug when filing out extension
Jan Vrany <jan.vrany@labware.com> [Fri, 29 Jan 2021 08:49:31 +0000] rev 920
Fix nasty bug when filing out extension When filing out extensions and using packages' original working copy, extension methods' source must be made local (just as for ordinary class methods). However, this MUST be done BEFORE a stream for extensions is opened otherwise it may have been truncated before `#makeLocalStringSource` is called.
Thu, 17 Dec 2020 12:16:18 +0000 Fix long standing bug in parsing node ids starting with long sequence of decimal numbers
Jan Vrany <jan.vrany@labware.com> [Thu, 17 Dec 2020 12:16:18 +0000] rev 919
Fix long standing bug in parsing node ids starting with long sequence of decimal numbers
(0) -300 -100 -10 +10 tip