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
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 fluca1...@infinito.it wrote:
Hi all,
this could sound
On Wed, Aug 26, 2015 at 8:28 AM, Luca Ferrari fluca1...@infinito.it 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?
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 comes into my mind is for aborting, is
that correct?
Thanks,
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 haj...@shaw.ca wrote:
I am using fossil under Windows 7.
After I check-in some files to fossil, a notepad-window pops up to
On 26 August 2015 at 04:27, Luca Ferrari fluca1...@infinito.it 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
On Wed, Aug 26, 2015 at 11:14 AM, Wayne Hajas haj...@shaw.ca 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
On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com 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?
On Wed, Aug 26, 2015 at 9:00 AM, Stephan Beal sgb...@googlemail.com 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
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
Hi Warren,
On Aug 26, 2015, at 5:28 PM, Warren Young w...@etr-usa.com wrote:
On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com
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.
11 matches
Mail list logo
