Re: [fossil-users] Replacing subversion revision number... by what?

On Dec 27, 2017, at 4:42 PM, Warren Young wrote: > > What it’s going to give you is a short prefix of the Fossil checkin ID On reading the script, it depends on being installed in a directory one level below the checkout root. I have it in a “tools” subdirectory of that

Re: [fossil-users] Replacing subversion revision number... by what?

On Dec 27, 2017, at 4:42 PM, Warren Young wrote: > > Here’s one my solutions to problems of this sort: > >https://tangentsoft.com/pidp8i/artifact/b7c1181a86483d86 Better URL: https://tangentsoft.com/pidp8i/file/tools/version > run it within the repository I mean the

Re: [fossil-users] Replacing subversion revision number... by what?

On Dec 27, 2017, at 3:06 PM, Olivier Mascia wrote: > > Coming from subversion where there is a revision number… I’ve made the same move with three separate repositories, and each time such a question has come up, I’ve chosen to simply not try to replicate the Subversion way

Re: [fossil-users] Replacing subversion revision number... by what?

> Le 28 déc. 2017 à 00:07, bch a écrit : > > The chain-length method Joerg mentioned is roughly what I was thinking, > bounded to a single branch “namespace” to manage disambiguation. Mind, this > is off the top of my head, not a thing I’ve implemented. Thanks Brad. --

Re: [fossil-users] Replacing subversion revision number... by what?

On Wed, Dec 27, 2017 at 2:23 PM Olivier Mascia wrote: > > Le 27 déc. 2017 à 23:10, bch a écrit : > > > > On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia wrote: > > Hello, > > > > Coming from subversion where there is a revision number,

Re: [fossil-users] Replacing subversion revision number... by what?

On Wed, Dec 27, 2017 at 10:10:21PM +, bch wrote: > On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia wrote: > > > Hello, > > > > Coming from subversion where there is a revision number, incremented by > > one by each commit, > > > > Let me be the first of many to say that

Re: [fossil-users] Replacing subversion revision number... by what?

> Le 27 déc. 2017 à 23:10, bch a écrit : > > On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia wrote: > Hello, > > Coming from subversion where there is a revision number, incremented by one > by each commit, > > > Let me be the first of many to say

Re: [fossil-users] Replacing subversion revision number... by what?

On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia wrote: > Hello, > > Coming from subversion where there is a revision number, incremented by > one by each commit, Let me be the first of many to say that those centrally controlled increments are not possible in a *distributed*

[fossil-users] Replacing subversion revision number... by what?

Hello, Coming from subversion where there is a revision number, incremented by one by each commit, which is very easy to capture in automated builds to be injected as part of the version number of binaries built... Revision 8745 -> version x.y.z.8745 Revision 8789 -> version x.y.z.8789 The

Re: [fossil-users] Import --svn "internal error: out of memory"

Am 27.12.2017 um 16:23 schrieb Warren Young: > On Dec 27, 2017, at 6:49 AM, Stephan Beal wrote: >> To quote the Oracle: >> >> "[Because] You didn't come here to make the choice, you've already made it. >> You're here to try to understand why you made it.” > Also, “Realize

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Am 27.12.2017 um 17:37 schrieb Olivier Mascia: > What Fossil version(s) does Fuel works with? I haven't seen a definitive list but I'm currently using the latest 2.4 (downloaded from fossil HP). So far I never had issues with whatever fossil version I was using since 1.34 (or so), so I never

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

> Le 27 déc. 2017 à 17:25, Chris Drexler a écrit : > >> If you are unable to make contact, you might consider "forking" the project >> (under a new name) and maintaining it yourself. > > The project is currently available at > >

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Am 27.12.2017 um 04:39 schrieb Ron W: > If you are unable to make contact, you might consider "forking" the > project (under a new name) and maintaining it yourself. The project is currently available at     https://server.ac-drexler.de/fossil/fuel if anyone is interested. Chris

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

Hi *, Am 27.12.2017 um 16:19 schrieb Warren Young: > On Dec 26, 2017, at 8:39 PM, Ron W wrote: >> If you are unable to make contact, you might consider "forking" the project >> (under a new name) and maintaining it yourself. > If it’s truly abandoned, you generally want to

Re: [fossil-users] Import --svn "internal error: out of memory"

On Dec 27, 2017, at 6:49 AM, Stephan Beal wrote: > > To quote the Oracle: > > "[Because] You didn't come here to make the choice, you've already made it. > You're here to try to understand why you made it.” Also, “Realize that there is no spoon. There is only fork.”

Re: [fossil-users] question regarding fuel-scm maintenance / ownership

On Dec 26, 2017, at 8:39 PM, Ron W wrote: > > If you are unable to make contact, you might consider "forking" the project > (under a new name) and maintaining it yourself. If it’s truly abandoned, you generally want to keep the name, unless it’s trademarked or “bad” in

Re: [fossil-users] Where would fossil.exe write some log when running as a service?

> Le 27 déc. 2017 à 14:49, Olivier Mascia a écrit : > > On one computer (running Server 2016), I have: > > fossil version -v > This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC > Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit) > > And I can

Re: [fossil-users] Where would fossil.exe write some log when running as a service?

> Le 27 déc. 2017 à 15:52, Olivier Mascia a écrit : > >> Le 27 déc. 2017 à 14:49, Olivier Mascia a écrit : >> >> On one computer (running Server 2016), I have: >> >> fossil version -v >> This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC

Re: [fossil-users] Where would fossil.exe write some log when running as a service?

> Le 27 déc. 2017 à 14:49, Olivier Mascia a écrit : > > On one computer (running Server 2016), I have: > > fossil version -v > This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC > Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit) > > And I can

[fossil-users] Where would fossil.exe write some log when running as a service?

Dear, On one computer (running Server 2016), I have: fossil version -v This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit) And I can run it as a service: fossil winsrv show fossil Service name

Re: [fossil-users] Import --svn "internal error: out of memory"

On Wed, Dec 27, 2017 at 12:44 PM, Olivier Mascia wrote: > Being "rookie" with Fossil, I'm starting some tests to migrate some of our > subversion repositories to Fossil and have a better test bed to learn > fossil before eventually deciding on a switch. > To quote the Oracle:

Re: [fossil-users] Import --svn "internal error: out of memory"

> Le 27 déc. 2017 à 13:22, Olivier Mascia a écrit : > >> But the fossil import turned short after about 3200 revisions (and about 10 >> minutes too) as such: >> >> C:\Develop\Fossil>fossil import --svn integral.fossil integral.dump >> Importing SVN revision: 3203 >>

Re: [fossil-users] Import --svn "internal error: out of memory"

> Le 27 déc. 2017 à 12:44, Olivier Mascia a écrit : > > Dear, > > Being "rookie" with Fossil, I'm starting some tests to migrate some of our > subversion repositories to Fossil and have a better test bed to learn fossil > before eventually deciding on a switch. > > I have

[fossil-users] Import --svn "internal error: out of memory"

Dear, Being "rookie" with Fossil, I'm starting some tests to migrate some of our subversion repositories to Fossil and have a better test bed to learn fossil before eventually deciding on a switch. I have successfully migrated a rather small (and secondary) repository with only some hundreds