Thu, 14 Mar 2019 04:31:42 +0000 update tags
convert-repo [Thu, 14 Mar 2019 04:31:42 +0000] rev 870
update tags
Wed, 13 Mar 2019 22:25:30 +0100 #REFACTORING by cg cvs_MAIN
Claus Gittinger <cg@exept.de> [Wed, 13 Mar 2019 22:25:30 +0100] rev 869
#REFACTORING by cg class: HGRemote changed: #displayString
Wed, 13 Mar 2019 22:23:24 +0100 #REFACTORING by cg cvs_MAIN
Claus Gittinger <cg@exept.de> [Wed, 13 Mar 2019 22:23:24 +0100] rev 868
#REFACTORING by cg class: SCMAbstractCommitDialog changed: #defaultSubtitle
Thu, 07 Mar 2019 12:22:12 +0000 Issue 256: fix parsing branch list when branch name(s) contains spaces
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 07 Mar 2019 12:22:12 +0000] rev 867
Issue 256: fix parsing branch list when branch name(s) contains spaces Since branch names may contain space, we must use custom template to get a a robust machine readable output. However, this is supported since Mercurial 3.5 (including) so for older Mercurials, we still use old code as a courtesy to users who may have old Mercurials. Las lomng as branch has no spaces, it should just work.
Tue, 08 Jan 2019 09:35:11 +0000 Issue 256: fix parsing branch name from changelog
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 08 Jan 2019 09:35:11 +0000] rev 866
Issue 256: fix parsing branch name from changelog To retrieve a branch of an changeset, `stx:libscm` uses `{branch}` branch keyword and then parses it as "name list". However, according to documentation it is a single string: branch String. The name of the branch on which the changeset was committed. This obviously caused problems when branch name had spaces in it. This commit fixes the problem. One remaining thing is that `stx:libscm` technically allows a changeset to be in more than one branch which seems to be impossible in Mercurial itself. This should be investigated and fixed, eventually.
Thu, 10 Jan 2019 21:25:14 +0000 Fix commit with class renames for Mercurial 4.8 and later
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 10 Jan 2019 21:25:14 +0000] rev 865
Fix commit with class renames for Mercurial 4.8 and later Starting with Mercurial 4.8 one has to use `-f` option to force rename of file over a file that is already tracked, otherwuse `hg mv` fails. This is tested by `#test_commit_17h`. This commit fixes this issue.
Tue, 13 Nov 2018 15:43:08 +0100 Issue #239: Fix all Smalltak/X source files to be in unicode (UTF8 without BOM) and prefixed by "{ Encoding: utf8 }" when any unicode character is present
Patrik Svestka <patrik.svestka@gmail.com> [Tue, 13 Nov 2018 15:43:08 +0100] rev 864
Issue #239: Fix all Smalltak/X source files to be in unicode (UTF8 without BOM) and prefixed by "{ Encoding: utf8 }" when any unicode character is present - All source *.st files are now Unicode UTF8 without BOM Files are in two groups (fileOut works this way in Smalltalk/X): - containing a unicode character have "{ Encoding: utf8 }" at the header - ASCII only are without the header
Thu, 11 Oct 2018 09:32:34 +0200 Fix `HGRevisonInfo >> #date` to return correct date
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 11 Oct 2018 09:32:34 +0200] rev 863
Fix `HGRevisonInfo >> #date` to return correct date Oops, due to a wrong format specification, the returned string was completely bogus! This commit fixes this and makes sure the date can be then parsed to an instance of a `Date` using `Date class >> readFrom:`
Tue, 25 Sep 2018 12:47:30 +0100 Added directory `objmingw` to default `.hgignore`
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 25 Sep 2018 12:47:30 +0100] rev 862
Added directory `objmingw` to default `.hgignore` ...generated upon first commit (or when there's no `.hgignore`)
Tue, 25 Sep 2018 12:33:31 +0100 Partial fix for "null" `HGChangeset`
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 25 Sep 2018 12:33:31 +0100] rev 861
Partial fix for "null" `HGChangeset` "null" changeset is currently kept as a singleton instance, i.e., `HGChangeset null` always return the same object. However, some queries (such as `#isObsolete` or `#successors`) require repository to be set - obviously, for "null" changeset there's no repository. Therefore these queries resulted into DNU. To paetially fix this, short-circuit these query methods to answer trasonable values for "null" changeset. Better solution would be to make "null" changeset a normal changeset within a repository.
(0) -300 -100 -10 +10 tip