Re: [fossil-users] Fossil added to AstLinux

2015-08-26 Thread Lonnie Abelbeck
Hi Warren, On Aug 26, 2015, at 5:28 PM, Warren Young wrote: > On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck > wrote: >> >> we wondered if it could be used to track changes to these configuration >> files in a way a non-developer type could easily understand. > > Did you look at etckeeper, an

Re: [fossil-users] Fossil added to AstLinux

2015-08-26 Thread Warren Young
On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck wrote: > > we wondered if it could be used to track changes to these configuration files > in a way a non-developer type could easily understand. Did you look at etckeeper, and if so, why did you reject it? https://joeyh.name/code/etckeeper/ > Lo

[fossil-users] Fossil added to AstLinux

2015-08-26 Thread Lonnie Abelbeck
Hi Richard and Fossil folks, I'm Lonnie Abelbeck, a developer with the AstLinux Open Source project ( http://www.astlinux.org ) an x86 image, only 50 MB in size, geared primarily to implement the Asterisk PBX, but we do a lot more than just a PBX. Richard kindly requested I forward some info he

Re: [fossil-users] SVN-fs-dump-format-version: 3 will produce unusable blobs

2015-08-26 Thread Baruch Burstein
I am sorry it took me so long to get to this. I don't know if it is still relevant for you, but I fixed this here: http://fossil-scm.org/index.html/info/24048eadf9247452 -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list

Re: [fossil-users] Carriage-return/line-feed issues

2015-08-26 Thread Ron W
On Wed, Aug 26, 2015 at 11:14 AM, Wayne Hajas wrote: > Later, I look at the time-line for the repository, and all the line-breaks > are gone from my change-description. It is all one run-on paragraph. > Go to the admin page in the web UI, then go to the time line settings page and check "*Allow

Re: [fossil-users] why merge does not prompt for commit?

2015-08-26 Thread David Mason
On 26 August 2015 at 04:27, Luca Ferrari wrote: > > Correct! > Shame on me. Not shame, at all! Some of the reasons for things are useful to think about, and because a popular system (e.g. GIT) does it a particular way can make us think it is the right way without thinking carefully. I didn't

Re: [fossil-users] Carriage-return/line-feed issues

2015-08-26 Thread Johan Kuuse
I would try configure Fossil on Windows to use Wordpad instead of Notepad. Wordpad does not need CR to treat NL properly. BR, Johan On Aug 26, 2015 5:14 PM, "Wayne Hajas" wrote: > I am using fossil under Windows 7. > > After I check-in some files to fossil, a notepad-window pops up to let me > d

[fossil-users] Carriage-return/line-feed issues

2015-08-26 Thread Wayne Hajas
I am using fossil under Windows 7. After I check-in some files to fossil, a notepad-window pops up to let me describe the changes that have been made. Later, I look at the time-line for the repository, and all the line-breaks are gone from my change-description. It is all one run-on paragrap

Re: [fossil-users] why merge does not prompt for commit?

2015-08-26 Thread Luca Ferrari
On Wed, Aug 26, 2015 at 9:00 AM, Stephan Beal wrote: > > Committing without first checking whether the commit was _semantically_ > successful is _just plain wrong_. git does it that way, but that is a huge > flaw in its thinking (IMHO). A successful merge only means that the SCM was > capable of m

Re: [fossil-users] why merge does not prompt for commit?

2015-08-26 Thread Stanislav Paskalev
Would you trust a merge algorithm that you software is correct post-merge ? Even if there are no merge conflicts there is no way to know whether the result is correct :) Stanislav Paskalev On Wed, Aug 26, 2015 at 9:28 AM, Luca Ferrari wrote: > Hi all, > this could sound trivial, but why the merg

Re: [fossil-users] why merge does not prompt for commit?

2015-08-26 Thread Stephan Beal
On Wed, Aug 26, 2015 at 8:28 AM, Luca Ferrari wrote: > Hi all, > this could sound trivial, but why the merge (especially with > --integrate) does not prompt immediately for a commit? What is the > rationale of having merge and commit as separate actions when closing > branches? The only one that