I am using two user accounts on a Linux box (Slackware64-13.37). I'm
getting an error when trying to clone a repo made by one user as another
user. Here is how it happens :
1. I create a new fossil repo while being logged as first user:
$ fossil new -A user1 test.fossil
2. I open it:
$ fossil
Sorry for missing fossil version which I forgot to include into the
initial mail:
$ fossil version
This is fossil version 1.23 [957b17af58] 2012-08-08 11:25:57 UTC
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
What happens if you add:
fossil clone -A user2 http://user1@localhost:8080
http://localhost:8080test.fossil
I am getting exactly the same behavior (cloning aborts) after I get
prompted for a password and enter it.
I tend to tighten up the permissions on my external repos so
Of course I can parse the timeline, get all revisions for a branch,
manually update the working directory to each of them and then commit them
to a new empty repository, but that's a lot of additional work. Maybe
fossil can do this on its own?
I know this sounds like an XY problem but I see no
It is possible to decouple a branch, in theory. But the command to do
so
has never been written. On the other hand, it probably wouldn't be all
that hard. What don't you give it a go and submit it as a patch?
On Wed, Aug 29, 2012 at 5:18 PM, v...@lavabit.com wrote:
Of course I can parse
I have a fossil repository where I keep my vim settings in different
branches. Here is an example output of branch listing:
$ fossil branch
* trunk
vim-7.3.000-i486-1-custom
vim-7.3.000-i486-1-default
vim-7.3.154-x86_64-1-custom-big
Now, to checkout the last branch in this list, I have to
On Mon, Aug 27, 2012 at 12:35 PM, Stephan Beal
sgb...@googlemail.comwrote:
On Mon, Aug 27, 2012 at 6:07 PM, v...@lavabit.com wrote:
I'd be very happy if I could just type:
$ fossil co vim-7.3.154
I'd be even happier if I could just type:
$ fossil co 154
Not to sound too pessimistic,
Hi!
This can currently be done with the JSON interface. Here's an example:
http://fossil.wanderinghorse.net/repos/fwiki/editor/wiki-editor-goco.html?page=README.goco
click on the Timeline tab, then on one of the version numbers on the
left
(b0b7a, currently the top one, looks good). That
On Thu, Aug 2, 2012 at 7:01 PM, v...@lavabit.com wrote:
succeed adding it to a fossil repo so I can use its functionality in
wiki
pages (like I managed to do with a custom source code highlighter long
ago).
The custom pages/commands feature, currently very early in development,
should
Since the functionality mentioned in subj is already implemented and works
for code diffs between revisions, is it possible to have it in wiki pages?
Maybe a custom markup convention that would allow adding two code snippets
and having them rendered as side-by-side diffs in wiki pages?
I'd really
I have an use case while I have to add many small files many times to a
fossil repository. So after doing fossil add many filenames I get a lot
of
ADDED filename
lines dumped to stdout.
After that, when doing fossil status I get these lines again.
Checking files one by one (to see if I didn't
But the output is not a side-by-side diff. Would love to have that as an
option, though! Perhaps even the default option!
--
D. Richard Hipp
d...@sqlite.org
Fine as long as current layout stays as option and doesn't get removed
just for the sake of keeping the fossil binary as small as
(2) Don't use shun. Even if you think you know what you are doing, you
are
very likely to get into trouble.
Learn from my mistake: Don't shun on a whim. The only reason to shun is
to
remove truly harmful content, such as spam. I should have just let the
sync
proceed even if it was
On Sun, May 22, 2011 at 6:17 PM, Ambrose Bonnaire-Sergeant
abonnaireserge...@gmail.com wrote:
I personally would be interested in any advancements you make with
javascript, or any other improvements from the basic fossil ui.
Me as well. If you extend the GoCo theme to include diff
I am using fossil tickets as TODO items for new features that must be
implemented. Often, I realize that I can break a new feature into smaller
sub-features. So, logically, the plan changes from
- Ticket A
to
- Ticket A
- Ticket A.1
- Ticket A.2
This can be recursive, so the initial
15 matches
Mail list logo
