2011/11/13 Lluís Batlle i Rossell vi...@viric.name
I agree with Julian. There should be an answer, if the letter does not
reach the
list. I also like when it is not required to subscribe to send mails.
In my experience, requiring subscription cuts down greatly on the amount of
noise and
Hello I've been trying out fossil, and cam across two things so far that
don't seem quite right. Could anyone advise if I am doing something wrong?
*Creating a branch*
When I use:
fossil commit --branch New Branch - m Creating a new branch
a new branch is created without a prompt, but when I
On Mon, Nov 14, 2011 at 12:17 PM, David Bovill da...@vaudevillecourt.tvwrote:
*Empty Folders*
When switching between branches, files are removed but empty folders are
left hanging around. Empty folders also do not show up with fossil
extras. I'm looking to switch between branches, and not
Thanks for that. Is the behaviour I am seeing for creating new branches
using:
fossil branch new Minimal trunc
normal (always asking for a pgp signature), or am I making a syntax error
somewhere? I've just upgraded to the latest build and ran fossil all
rebuild, but get the same behaviour?
On
On Mon, Nov 14, 2011 at 6:56 AM, David Bovill da...@vaudevillecourt.tvwrote:
Thanks for that. Is the behaviour I am seeing for creating new branches
using:
fossil branch new Minimal trunc
normal (always asking for a pgp signature), or am I making a syntax error
somewhere? I've just
On 14 November 2011 12:05, Richard Hipp d...@sqlite.org wrote:
fossil branch new simply creates a new check-in which is unchanged from
the previous check-in. It is equivalent to doing:
fossil commit -f --branch Minimal
OK - thanks, the --force option will get me what I need.
On Mon, 14 Nov 2011 12:32:40 +0100
Stephan Beal sgb...@googlemail.com wrote:
[...]
Fossil doesn't track directories. If you want to get rid of empty
ones, one way to do this in Unix is:
find . -type d | xargs rmdir
Notes:
a) rmdir will refuse to delete non-empty dirs, so the above will
The side-by-side diffs are great, but I can't get the command line
options (--side-by-side|-y
side-by-side http://www.fossil-scm.org/fossil/help/diff) working. Both
these fail:
fossil diff --from previous --to current --side-by-side hello.txt
fossil diff --from previous --to current -y hello.txt
Hi all,
I'm attempting to export a fossil repo to git.
However, I get the following error on git import:
fatal: mark :51 not declared
Full crash log is here: https://gist.github.com/1363907
Fossil version: both latest master and 2011-10-21
Git version: 1.7.5.4
OS: Debian Linux 6.0
I've tried
On Sun, 2011-11-13 at 12:50 -0500, Richard Hipp wrote:
On Sun, Nov 13, 2011 at 6:39 AM, ST smn...@gmail.com wrote:
Hi,
I'm new to fossil and have several questions:
1) how do I open new tickets on fossil-scm.org? I didn't see
something
(on fossil 1.20)
I've renamed a file, and modified the new one without any commit in the middle,
and then 'fossil status' or 'fossil commit' do not show that it *removes* the
old name.
Regarding a revert of that change in the working copy, it deletes the 'new
file', but does not restore the
It's fixed now; I don't know why it works, but it does work. I did the
following:
1. Delete the local fossil repository
2. Remove the _FOSSIL_ file from the local checked out directory.
3. fossil clone the server repository
4. fossil open into the local checked out directory
5. fossil add * all
Hi all,
A best practice question:
What is the preferred way to include external libraries in a fossil
repository? I mean larger dependencies like boost.
For small libs and tools like a few binary or source code files, I
tend to include them directly in the repo but for larger ones it
doesn't
Hello,
another one!
I was in a branch. I added a file (wrote it, and fossil add file).
I decided I wanted to commit in another branch; fossil update branch. And fossil
removed the file I was about to commit.
Luckily 'fossil undo' helped... Worth fixing though.
(fossil 1.20)
Regards,
Lluís.
On Mon, Nov 14, 2011 at 03:21:30PM +0100, Lluís Batlle i Rossell wrote:
I was in a branch. I added a file (wrote it, and fossil add file).
I decided I wanted to commit in another branch; fossil update branch. And
fossil
removed the file I was about to commit.
Luckily 'fossil undo'
I added the same file that I had removed in a previous checkin. THe new checkin
looks like this in the UI:
Changes
--
show unified diffs show side-by-side diffs patch
Added CMakeLists.txt version [23aa5af411789697]
Added CMakeLists.txt version [23aa5af411789697]
The manifest is a delta
Lluis,
That's the same issue I noted in my email from Oct 25 (subject: mv +
revert irregularity) and it contains a short shell script demonstrating
the problem as you stated. It's not clear what the proper behavior is on
revert of this kind; I sent a reminder email regarding the issue
On Nov 14, 2011, at 3:19 PM, Jacek Cała wrote:
A best practice question:
What is the preferred way to include external libraries in a fossil
repository? I mean larger dependencies like boost.
For small libs and tools like a few binary or source code files, I
tend to include them directly in
I'd like to know more about this as well. As I understand it you can nest
fossil repositories, I haven't tried it yet, but AFAIK you can have a
nested checkout within an existing checkout, and you can open it with the
fossil open --nested command.
2011/11/14 Jacek Cała jacek.c...@gmail.com
Hi
On Mon, Nov 14, 2011 at 11:11 AM, David Bovill da...@vaudevillecourt.tvwrote:
I'd like to know more about this as well. As I understand it you can nest
fossil repositories, I haven't tried it yet, but AFAIK you can have a
nested checkout within an existing checkout, and you can open it with
On Sun, Nov 13, 2011 at 4:33 PM, Julian Fagir listensamm...@komkon2.de wrote:
So, my question: Do you think fossil is appropriate?
It really depends on your and your customers' needs. It works well for
decent number of projects. Certainly has has served the needs of the
projects my coworkers
21 matches
Mail list logo
