1- If someone wants to create a new cvs2fossil, what command can be
used to commit a
file with an ancient date?
2- How to revert a file to a different version but saving with a
different name?
___
fossil-users mailing list
Oh. I didn't know about these (while writing cvs2fossil). Which is why I put
this information into the new commit message. Since when do they exist ?
Andreas, I see that you are the developer of cvs2fossil. I have tried it and I
have had some problems with it (the details are in another
what
happens.
2009/10/7 Andreas Kupries andre...@activestate.com:
Ramon Ribó wrote:
Oh. I didn't know about these (while writing cvs2fossil). Which is why I put
this information into the new commit message. Since when do they exist ?
Andreas, I see that you are the developer of cvs2fossil
:
Please send the orrect attachment. The only file I see is to change cvsroot
in cvs repository.
- Altu
- Original Message -
From: Ramon Ribó ram...@compassis.com
To: fossil-users@lists.fossil-scm.org
Subject: [fossil-users] importing from cvs
Date: Tue, 13 Oct 2009 10:02:34 +0200
Hello,
In my opinion it would be nice to extend a bit the fossil markup to
make it a subset of creole. Specifically I would add:
1) **bold** and //italics// (nicer than the b thing)
2) relax the specification of 2 spaces around '*' and '#' for making
lists. What is
the problem with
open with Notepad.
4- The file is viewed as with one very long line
I am sure that I can find much more examples.
2009/10/21 Joshua Paine jos...@letterblock.com:
On Wed, 2009-10-21 at 16:36 +0200, Ramon Ribó wrote:
In any case, what is your proposal for using fossil to manage a program
echo $contents | dos2unix
fi
else
echo $contents
fi
2009/10/21 Joshua Paine jos...@letterblock.com:
On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote:
1- A TCL file is checked in on windows
2- It is checked out on unix and line ending is \r\n
When the file is created on Windows
Maybe in the files section of the web, you can add a link to:
Download zip of last checkin
2009/10/21 D. Richard Hipp d...@hwaci.com:
On Oct 21, 2009, at 1:03 PM, Wilson, Ronald wrote:
Other Links: files | ZIP archive | manifest
I never noticed that - and the zip has all the code
I mean last checkin of the trunk
Then, in the branches page there could be the possibility of downloading
the last checkin of every branch
2009/10/21 Dmitry Chestnykh dch...@gmail.com:
On 21.10.2009, at 21:23, Ramon Ribó wrote:
Maybe in the files section of the web, you can add a link
In practical terms, it is very annoying and confusing to go to the
files section and see that the file that we introduced by error
several years ago and immediately after deleted, is listed there as a
normal file.
In my opinion, the best option would be to list by default the files
of the last
tel. +34 93 218 19 89
08006 Barcelona, Spainfax. +34 93 396 97 46
2009/12/9 Joshua Paine jos...@letterblock.com:
On Wed, 2009-12-09 at 23:41 +0100, Ramon Ribó wrote:
An option that I would like to see in fossil, as it is not easy to
perform in fossil without changing any file
?), but with the added complexity for the final user. One more
option to read in the help, one more option to remember...
RR
2009/12/9 Stephan Beal sgb...@googlemail.com:
On Wed, Dec 9, 2009 at 11:41 PM, Ramon Ribó ram...@compassis.com wrote:
category. I do not see it useful for scripting or external tools
... because it means more users. More users = better
testing. Better testing = less problems for you and I.
Sure? And the pleasure of using an elite tool, far away from the masses?
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ram...@compassis.com
c/
If I then do
rm *.foo
when I meant to do
fossil rm *.foo
I can then do
fossil update
which will give me my *.foo files back.
Are you sure that this command is going to give that files back? Have
you tried it?
This is another field where there are currently proposals to
Hm, I just browsed the man pages of many VCS systems (CVS included) to find
examples of parameters for the message file. I had no problem locating their
pages, browsing the manual and finding them for 6 VCS systems in about 3
minutes.
You must be cleverer than me ... or I felt my 3
What I meant was the following:
rm file1
fossil update
in others VCS like CVS, file file1 would appear again on disk. in
fossil it does not.
fossil revert file1
Now, it appears on disk
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ram...@compassis.com
c/
In fact, fossil is saying that the merge between a file and a
deleted file is a deleted file. Which is something to what I would
strongly agree.
RR
2009/12/11 Will Duquette w...@wjduquette.com:
On Dec 11, 2009, at 6:48 AM, Ramon Ribó wrote:
What I meant was the following:
rm file1
A reasonably modern computer can compute these fast enough
to break most user passwords in a couple of minutes. What PBKDF2 does is
use a function that is purposely expensive to make the dictionary attack
I just described impractical.
Anyone minimally concerned with security, will use a
I think that fossil solution of using a simple file __FOSSIL__ in the
root directory
is a far superior solution than the classical of creating a directory
for the SCM.
The only point is that files manifest and manifest.uuid should not be there
by default in new projects. Only people actively
2010/1/21 Daniel Carrera dcarr...@gmail.com:
Ramon Ribó wrote:
I think that fossil solution of using a simple file __FOSSIL__ in the
root directory is a far superior solution than the classical of creating
a directory for the SCM.
Why? Even if you get rid of manifest and manifest.uuid you
Define last committed leaf in a distributed system. Even if you can, it
may be on a branch you don't care about, the repository has no way of
telling.
last committed leaf
Definition 1: It is the Open leaf with most recent commit date in
current repository
Definition 2: It is the first row in
This is a problem already discussed. The files section of the web
interface become a mess when people rename or delete files.
In my personal opinion, the files section should point, by default, to
the active files in the last commit in the trunk. (and give a link to
go to other versions or to ALL
://www.compassis.com/c/ramdebugger/index
http://www.compassis.com/c/ramdebugger/indexRegards,
Ramon Ribó
2010/4/25 Ron Aaron r...@ronware.org
I seem to recall something like that, but can't find the reference.
I'm interested in that, maybe in helping out.
--
For privacy, my GPG key signature
Hello,
RamDebugger has some support for GUI commit add update in cvs
and fossil. It is an IDE debugger for TCL
http://www.compassis.com/ramdebugger
http://www.compassis.com/c/ramdebugger/index
Regards,
Ramon Ribó
2010/7/1 Stephen De Gabrielle stephen.degabrie...@acm.org:
I
is putty:
http://www.putty.org/
It contains a command line tool, named plink, very similar to ssh
For testing, it is also possible to install putty on Linux.
Ramon Ribó
2010/8/26 Richard Hipp d...@sqlite.org
Using the templates provided by boytm here: (
http://www.fossil-scm.org/fossil/info
Sistemas Dr. Ramon Ribo
http://www.compassis.com ram...@compassis.com
c/ Tuset, 8 7-2 tel. +34 93 218 19 89
08006 Barcelona, Spainfax. +34 93 396 97 46
El 27/08/2010 03:52, Richard Hipp d...@sqlite.org escribió:
On Thu, Aug 26, 2010 at 11:22 AM, Ramon Ribó
Since tickets are configurable on a site-by-site basis, I is difficult to
imagine
what a command-line interface to the ticketing system might look like. Do
you have any suggestions?
Yes, I do.
I've developed a GUI for fossil (inside RamDebugger), that permits to select
an open ticket and add
fossil.exe ticket show REPORTNR ?TICKETFILTER? ?-l|--limit LIMITCHAR?
What is REPORTNR?
I think it should fulfill most requirements, even linking an external gui to
the fossil application
How do you list all tickets that are not closed or fixed, with its
basic data of:
for the addition to fossil. This new feature looks
very nice and will be useful for automated GUI's. I hope that it will
be moved soon to the trunk
RR
2010/10/5 wolfgang rat...@stumvolls.de:
Ramon Ribó ram...@... writes:
In the newest version, you can call the report by its name
08006 Barcelona, Spain fax. +34 93 396 97 46
2010/10/6 Wolfgang rat...@stumvolls.de:
Ramon Ribó ram...@... writes:
:
This new version looks very nice to be used by a GUI. A couple of comments:
1- fossil.exe ticket list
Would it be better something like?:
fossil.exe
A quick google search finds more fieldlist than fieldslist entries, so i
tend to use fieldlist.
Then, if we have google veredict, it should be definitive!!!
RR
2010/10/6 Wolfgang rat...@stumvolls.de:
Ramon Ribó ram...@... writes:
what is your opinion between these two alternatives
It sounds very nice !!
-RR
2010/10/7 Wolfgang rat...@stumvolls.de:
Eric e...@... writes:
:
fossil ticket fields
depending on the rest of the possible syntax.
:
With checkin 3f06f272cd , i changed it to
fossil ticket list fields
and added
fossil ticket list reports
All
Also, It is not clear for me the difference between:
a - Admin: Create and delete users
and
s - Setup/Super-user: Setup and configure this website
Is it really necessary to have these two separated options? They
really confuse my co-workers
and myself
Ramon Ribó
2010/10/20 Wilson
Hello,
fossil import git
fossil import svn
fossil import hg
And so forth Thoughts?
In my opinion, this is the most correct option for several reasons:
1- Do not pollute the global namespace
2- Make it easier for everyone that is not going to use the option
The solution here is simple.
Create a installer script that will make a few tasks:
1- Update the internal script version number, based on the manifest
2- Create an installer or zip file
If you are a script programmer, you can develop that script in a few lines
of code. And you will discover
Hello,
In a related subject about merge, I think that fossil should give
more information in the merge marker lines in the files. I think that
it would be appropiate to explain, in each of the two versions of the
code, from which versions they come from or if they come from local
changes.
Why do not compact the 3 lines into one line?
RR
2010/12/15 Zach Todd zacht...@cis-partners.com:
I have updated some of the merge conflict code to provide a little more
detail. Below is an example of this update in action.
0
1
2
3
BEGIN MERGE CONFLICT
Hello,
We have had this problem in the past.
A simple workaround is to go to the server ui and edit by hand the
checkin, for example changing the commit date or the comment.
RR
El 22 de desembre de 2010 10:27, Lluís Batlle i Rossell
virik...@gmail.comha escrit:
We had a fossil
Hello,
Currently, there are a couple of tools in fossil that are useful to store
intermediate and private changes
for one developer: stash and commit --private
Both of these tools assume that the developer is going to work in a
unique computer.
Assuming the case that one developer
And this is what private commits are for. Work pretty well if you
have something, that you don't want to show. It's only a shame
they're not emphasized well in the docs (or at least were not the
last time I checked).
Private commits are useless if you work in more than one computer and
need
I do not agree here. Of course, the solution is:
a
c
b
It follows the principle of least surprise. If you want to make very
strange things with merges, do not use a tool with automatic merge. Do
it manually.
Also, the merge of two equal lines, one with unix line end and the
other with Windows
What can you do with:
fossil update ?VERSION? FILES...
That you cannot do easily with?
fossil revert ?-r REVISION? ?FILE ...?
Or I am missing something or fossil update files... is redundant.
RR
2011/3/17 Joshua Paine jos...@letterblock.com:
On Mar 17, 2011, at 11:00 AM, johnfound
MacOSX is using UNIX line ending since more than 10 years-ago.
In modern computers, there are two options:
Unix/MacOSX: LF
Windows: CR-LF
I would not see it as a problem that fossil changed line-endings if it
was disabled by default and it could be enabled with something similar
to:
fossil
and are having the CR-LF
problem as well as the code page problem.
An you know, big brother always is right, isn't it?
RR
2011/4/7 Richard Hipp d...@sqlite.org:
On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó ram...@compassis.com wrote:
MacOSX is using UNIX line ending since more than 10 years-ago
Do not worry Shaw, we shall manage to survive without you.
err... how much did you contribute to the project?
RR
2011/5/21 Zed A. Shaw zeds...@zedshaw.com:
On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote:
Problem fixed in the latest fossil checkin.
Sorry, but I can't have
to loose 3 days
work but it is not fair to accusse a free software development
community for this.
RR
2011/5/21 Ambrose Bonnaire-Sergeant abonnaireserge...@gmail.com:
On Sun, May 22, 2011 at 1:44 AM, Ramon Ribó ram...@compassis.com wrote:
Do not worry Shaw, we shall manage to survive without you
(4) The result should have a 0 Fail-Score according to
https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL
This point is not easy to acomplish. Take into acount the following
statement in the previous page:
You've written your own source control for this
To quote Donald Knuth: the root of all evil is premature optimization.
Although the quote is nice and applicable to many situations, I
think that this is absolutely not the case.
The problem is not to make a type of optimization, the problem is
that it is necessary to make a decision
solution, what other sub commands, appart
from install and remove do you really need?
I understand that start and stop can be managed automatically, or
for special cases, from the Windows GUI directly.
RR
2011/7/19 Thomas Schnurrenberger t...@gmx.net:
On 19.07.2011 17:47, Ramon Ribó wrote
, Thomas Schnurrenberger t...@gmx.net escribió:
On 19.07.2011 18:36, Ramon Ribó wrote:
Althouth winsvc could also be a good solution, what other sub commands,
appart
from install and remove do you really need?
You don't need the service command at all. There are command line
utilities
The use case is obvious: inform the user about the state of the SVC.
Once the user is aknowledged that there are changes to update/merge he can:
1- Merge them automatically
2- Check file by file manually to review the differences
3- Start a branch with own changes
4- Do not update and wait
BTW, to cancel changes made but not commited, is there a less radical
solution than force-closing/reopening the repository?
fossil help revert
RR
2011/10/4 Gilles gilles.gana...@free.fr:
On Tue, 4 Oct 2011 11:13:16 +0200, Lluís Batlle i Rossell
virik...@gmail.com wrote:
There may be some
It is not the job of the SCM system to keep in step with my working
directory
Why not? In that case, fossil update shouldn't delete files that
have been removed from repository, but it does.
Another issue is that an SCM system is _not_ a backup tool, but many
people seem to think that it is.
For me, much better with the colors. Maybe taking out the violet of the
hidden lines.
It helps a lot to focus the attention to the correct place.
RR
El 04/02/2012 13:24, Richard Hipp d...@sqlite.org escribió:
On Sat, Feb 4, 2012 at 5:08 AM, altufa...@mail.com wrote:
Same here. I like the
Additionally, fossil merge -n | grep will not find them, because they appear
at stderr.
What about?:
fossil merge -n | grep
RR
El 10 de febrer de 2012 10:30, Lluís Batlle i Rossell
vi...@viric.name ha escrit:
Hello,
I had troubles in a big merge of hundreds of files, where five filse
to make it work again.
RR
El 10 de febrer de 2012 10:54, Lluís Batlle i Rossell
vi...@viric.name ha escrit:
On Fri, Feb 10, 2012 at 10:47:21AM +0100, Ramon Ribó wrote:
Additionally, fossil merge -n | grep will not find them, because they
appear
at stderr.
What about?:
fossil merge -n
Hello,
Have you tried to see the differences page on Google Chrome? I see
them ok on firefox but very bad on chrome.
It looks like it does not preserve indentation.
RR
2012/2/16 Richard Hipp d...@sqlite.org:
2012/2/16 Lluís Batlle i Rossell vi...@viric.name
On Thu, Feb 16, 2012 at
In practice, set it to *. Its the only way to avoid problems if you
have a developers team both in Unix and Windows.
My recommendation is for fossil to have a default value of * for new
databases. One detail less to understand for the users.
RR
2012/2/27 Tomek Kott tkott.s...@gmail.com:
I
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil update current
(5) Unlimited undo (purgin old undos after a defined number of days)
(6) Explain in more detail the clock problems with the
in the timeline, branches section and files section
(files belonging only to hidden branches do not appear), unless a
special option to show hidden is selected. (useful to hide mistakes)
RR
2012/2/28 Leo Razoumov slonik...@gmail.com:
On Tue, Feb 28, 2012 at 07:59, Ramon Ribó ram...@compassis.com wrote
this would
be to mark some branches as of no interest anymore for day to day
work, except for archaeological purposes.
RR
2012/2/28 Konstantin Khomoutov flatw...@users.sourceforge.net:
On Tue, 28 Feb 2012 14:47:00 +0100
Ramon Ribó ram...@compassis.com wrote:
[...]
(9) in the web page
Hello,
RamDebugger is an IDE and Debugger for the TCL language. At the
same time, it is a GUI for cvs and fossil.
http://www.compassis.com/ramdebugger
http://www.compassis.com/c/ramdebugger/index
Completely unrelated to RamDebugger SCM capabilities with cvs and
fossil, RamDebugger
Leo,
I think that you have described fairly well the situation.
I am a Unix/Windows user since the Silicon Graphics time. I would never
put brackets on a file name. However, I fail to understand why the SCM tool
should prohibit to do so to people that think differently. Specially on
Hello,
Currently the help of fossil all says:
Respositories are automatically added to the set of known repositories
when one of the following commands are run against the repository: clone,
info, pull, push, or sync.
Would not be more logical that it where:
Respositories are
Wouldn't it be more logical that
fossil settings ignore-glob
followed the case criteria of:
fossil settings case-sensitive
?
RR
2012/4/13 Stephan Beal sgb...@googlemail.com
On Fri, Apr 13, 2012 at 3:10 PM, vince vinc...@neuf.fr wrote:
the option ignore-glob is case
Try vcs-ramdebugger:
http://www.compassis.com/ramdebugger/vcs-ramdebugger:%20Version%20control%20system%20for%20fossil
RR
2012/4/19 Gilles gilles.gana...@free.fr:
Hello
I find typing commands in a DOS box not as convenient as
right-clicking on a file/folder in Windows Explorer, to the
An interesting new capability for fossil could be the following:
That it allowed to have more than one tickets list, with different
tables and reports in every list. This could have several advantages:
1- Keep a completely separated list for bugs and for new features, for example
2- Use fossil
No. I mean that every list would have a different table schema with
different fields.
RR
2012/7/4 Lluís Batlle i Rossell vi...@viric.name:
On Wed, Jul 04, 2012 at 10:00:52AM +0200, Ramon Ribó wrote:
An interesting new capability for fossil could be the following:
That it allowed to have
I think that it is clear:
different list - different data requirements - different table fields
RR
2012/7/4 Lluís Batlle i Rossell vi...@viric.name:
On Wed, Jul 04, 2012 at 10:18:10AM +0200, Ramon Ribó wrote:
No. I mean that every list would have a different table schema with
different
Would it be possible that the prebuilt binaries where compiled with SSL?
(if necessary, including the dependency libraries)
RR
2012/8/6 Richard Hipp d...@sqlite.org
It has been a long time since we have done an official release of Fossil
with prebuilt binaries. We should probably do
Hello,
One simple solution, if using Linux, is sshfs. It creates a remote file
system in the local computer. Then, You can sync as if the remote file were
a local file. It works nicely.
Maybe the fossil ssh implementation can get some ideas from this package.
Ramon Ribó
2012/11/10 Martin
Sshfs didn't fix the problems that I was having with fossil+ssh, or at
least
only did so partially.
Why not? In what sshfs failed to give you the equivalent functionality than
a remote access to a fossil database through ssh?
2012/11/11 Timothy Beyer bey...@fastmail.net
At Sat, 10 Nov 2012
) Any use of that is not a recognized html tag consider it as
normal text
With a wise use of 2a) and 2b) there should be nearly no cases where a text
only comment is displayed bad.
Regards,
Ramon Ribó
2012/11/22 Jan Nijtmans jan.nijtm...@gmail.com
2012/11/22 Michal Suchanek hramr...@gmail.com
As I understand it, fossil currently deletes one file from disk when doing
and update if this file has been removed by another user.
For me, it is incoherent that fossil does not do the same on commit. Of
course, only for the case that there is a copy of the file in the previous
version and
(1) fossil rm xyx.txt will remove the file xyz.txt from disk if and only
if an exact copy of xyz.txt exists under control. If xyz.txt has been
modified or if xyz.txt has never been checked in (and the fossil rm is
simply to reverse a prior fossil add) then xyz.txt is unchanged. Either
way,
Well, yes, that is the way I do it too. I suspect that there are some
who do not review their changes before commit, and that many of those
commit way too often, essentially treating their VCS as a backup method.
This of course leads to junk, non-functional checkins, followed by an
unhealthy
Hello,
In my opinion, the private branch concept only works well for people
working in just one computer. In the every day more common case of
people developing in several computers (desktop, laptop, tablet, etc),
private branches do not adapt well to the situation. Probably the
solution could be
Hello,
Much nicer:
fossil add kk.cc
fossil commit -m v1
(some failed changes)
fossil commit -m failed attempt --branch failed_attempt
fossil update trunk
(some changes)
fossil commit -m good
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com
In my opinion, the solution is more simple. Instead of:
- sync
- stop if would fork
- commit
- sync
The procedure should be:
- commit
- sync
- rollback if would fork
Ramon Ribó
El 13/01/2013 13:11, Richard Hipp d...@sqlite.org va escriure:
On Sun, Jan 13, 2013 at 1:45 AM, Matt Welland
I completely agree with this and also the annotate algorithm should not
take into account the line endings
RR
2014-02-11 17:56 GMT+01:00 Tony Papadimitriou to...@acm.org:
Hi all,
While converting some text files from CRLF (Windows) to LF (Linux)
endings, and committing the changes, I
Hello,
One of the key points that make a software like fossil so good is the care
taken to define the interfaces. In general, they are minimalist and very
useful. It was the case for the annotate option in the web interface.
Clear, simple and useful.
In the last fossil versions, it has changed.
as either \n or \r\n and we do not mind
which of them is used.
In fact, if you open a text file in either C, C++ or in TCL (in text mode),
\r\n is converted into \n to all effects.
RR
2014-03-04 14:03 GMT+01:00 Stephan Beal sgb...@googlemail.com:
On Tue, Mar 4, 2014 at 12:57 PM, Ramon Ribó ram
I can agree to treat space at the end of line as a difference. However, the
end of line marker, be it \n or \r\n should be treated as equal. I
really cannot imagine a situation where this difference can be
significative.
Please note that languages like C, C++ or TCL do not distinguish between
Some points:
1- Would it be possible to write the list of analyzed ancestors after the
line origins list? (most useful information first)
2- Would it be possible to have option ignore whitespace activated by
defaut?
3- Would it be possible to make the ignore whitespace more persistent
between
The current Fossil implementation runs a separate process for each HTTP
request. So an in-memory cache wouldn't be helpful. It has to be disk-
based.
Does not FastCGI do exactly the opposite?
RR
2014-03-12 18:25 GMT+01:00 Richard Hipp d...@sqlite.org:
On Wed, Mar 12, 2014 at
This is really a great tool!
To be even better, it would be nice to have some keystrokes to
navigate through the differences. Just to mimic tkdiff, I propose:
letter n - go to the following difference
letter p - go to the previous difference
Also, there is a bug to correct: if pressing save as
Hello,
I've implemented in diff -tk a new capability and a bug fix:
- Keys 'p' and 'n' are used to navigate to the previous and next difference
- A bug fix in Save as when users cancels file selection
There is an attached patch with the code. Please feel free to use it
in any way in case you
Hello,
Thess commands gives an error:
fossil diff --verbose --tk
fossil diff -v --tk
shouldn't they work ok?
RR
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
GMT+02:00 Ramon Ribó ram...@compassis.com:
Hello,
Thess commands gives an error:
fossil diff --verbose --tk
fossil diff -v --tk
shouldn't they work ok?
fossil-scm.org/index.html/info/c060947196
Thanks!
Regards,
Jan Nijtmans
:00 Ramon Ribó ram...@compassis.com:
OK. Thanks. But I misunderstood the usage of this option. I thought
that it would print all the lines of the diff files, including the
equal ones. Is there another option to do it? Something like: -c
infinite?
http://fossil-scm.org/index.html/artifact
If autosync is activated, of course it should do it. In fact, I see it
as an error not doing it. Does not 'autosync' means: do all the pushes
and pulls necessary to keep local repository always syncronized with
remote repository?
RR
2014-10-10 0:04 GMT+02:00 Matt Welland estifo...@gmail.com:
NB// there are two general contexts for a merge, merge from a branch or
merge from a node. When merging from a node there is no ambiguity and this
conversation does not apply. However when merging from a branch there *is*
ambiguity. The don't sync crowd sees the merge as applying to the tip of
New test version contained in branch: tk-diff-viewer, behaves in the
following way:
http://fossil-scm.org/index.html/info/cbd4dca6807d95d73c22cb02893887efc1b51655
When there are no changes, the GUI opens with void differences and a
message in a window informs the user: No changes. In this way,
A possible workflow to do partial commits in fossil could be:
- fossil diff --tk --partial-commit
(A special version of fossil diff --tk appears where there is a
checkbox in every difference)
- Select some differences
- Save and quit
(Then, an automatic fossil stash is performed where the
-20 13:39 GMT+01:00 Stephan Beal sgb...@googlemail.com:
On Fri, Mar 20, 2015 at 11:24 AM, Ramon Ribó ram...@compassis.com wrote:
A possible workflow to do partial commits in fossil could be:
- fossil diff --tk --partial-commit
(A special version of fossil diff --tk appears where
that the partial commit can compile
Option b) it is allowed
Then, the user do whatever he likes to.
2015-03-20 13:46 GMT+01:00 Stephan Beal sgb...@googlemail.com:
On Fri, Mar 20, 2015 at 1:45 PM, Ramon Ribó ram...@compassis.com wrote:
A partial-file commit implies that one will commit untested
fossil version
This is fossil version 1.32 [302052d30b] 2015-02-20 08:30:51 UTC
fossil sync
Usage: c:\other\binutils\fossil.exe sync URL
is it not possible to use sync without URL?
RR
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Usage: c:\other\binutils\fossil.exe sync ?URL? ?options?
and the error message with:
fossil sync
Usage: c:\other\binutils\fossil.exe sync URL
RR
2015-03-17 17:23 GMT+01:00 j. van den hoff veedeeh...@googlemail.com:
On Tue, 17 Mar 2015 17:06:33 +0100, Ramon Ribó ram...@compassis.com wrote:
fossil
I completely agree to change current mv/rm commands so as they perform
the OS level operation too. It looks like an inconsistency that they
do not move/remove the file in the local repository and they
move/remove it in the cloned repositories.
If some script breaks, it can be repaired. No
I think that both worlds can live together without any problem.
- When doing fossil mv A B
* If A exists and B does not exist in file system, rename file A to B
* If B exists and A does not exist in file system, do nothing
* If either both exist or none exists, warn and stop
- When doing fossil
1 - 100 of 105 matches
Mail list logo
