CLASSIFICATION: UNCLASSIFIED
"One pithy way of saying this is that Git tries to show what you should have
done while Fossil tries to show what you actually did."
Indeed!
-Original Message-
From: fossil-users-boun...@lists.fossil-scm.org
[mailto:fossil-users-boun...@lists.fossil-scm.org
On Sun, Apr 24, 2016 at 12:33 PM, Marko Käning
wrote:
> Hi list,
>
> how can one migrate a repository's wiki pages to another repo?
>
Push will push all content changes, including public check-ins, and wiki,
ticket, and tech-note edits.
> One could imagine to have some ex/import functionality
Hello,
I have a fossil repository which is used only for tickets, and is
served on our intranet: users are using it through the web ui only.
The goal would be that users could go out of the society with
a copy of the database, fill new tickets directly on their computer, and
synchronise
their mo
On 4/25/16, Matthieu Dubuget wrote:
>
> I had to add "g Clone: Clone the repository" capability to allow users to
> clone the repository on their own computer. It seems logical.
> Here are the capabilities of my test user : bceghjnprw
>
>
> But it seems it is not enough: when `fossil ui` is starte
Le 25/04/2016 12:55, Richard Hipp a écrit :
> On 4/25/16, Matthieu Dubuget wrote:
>> I had to add "g Clone: Clone the repository" capability to allow users to
>> clone the repository on their own computer. It seems logical.
>> Here are the capabilities of my test user : bceghjnprw
>>
>>
>> But it
Le 25/04/2016 13:58, Matthieu Dubuget a écrit :
> matt@xps:~/projets/bmts$ ssh srvif ./fossil-1.34 user capabilities test -R
> bugsMetalscan.fossil
> qjr
Oh. Sorry. For some reason, I put 'q' instead of 'g'!
'g' allows to clone.
But as in my initial e-mail, the ticket table is not cloned. I trie
Might be misremembering, but don't the ticket schemas count as "config"
areas which need to be pulled once?
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Apr 25, 2016 12:35 PM, "Matthieu Dubuget"
wrote:
> Hello,
>
> I have a fossil
On 4/25/16, Stephan Beal wrote:
> Might be misremembering, but don't the ticket schemas count as "config"
> areas which need to be pulled once?
They get pulled automatically on a clone. After the initial clone,
then you have to do "fossil config pull ..." for updates.
The bitmask in the second
Le 25/04/2016 15:46, Stephan Beal a écrit :
>
> Might be misremembering, but don't the ticket schemas count as "config" areas
> which need to be pulled once?
>
If you mean :
./fossil-1.34 configuration pull all http://test@srvif:8085
It is the last test I did in the listing you quoted. Or is it
On 4/25/16, Matthieu Dubuget wrote:
>
> From my other tests, it seems that if the user who is cloning the repository
> has 'a' capability,
> he does not need to pull any additionnal configuration, to have a
> functionnal ticket system
> cloned, and able to push tickets modifications.
>
You should
On Apr 25, 2016 4:21 PM, "Matthieu Dubuget"
wrote:
>
> Le 25/04/2016 15:46, Stephan Beal a écrit :
> >
> > Might be misremembering, but don't the ticket schemas count as "config"
areas which need to be pulled once?
> >
>
> If you mean :
>
> ./fossil-1.34 configuration pull all http://test@srvif:80
I know that every time I mention this I get silently, perhaps even
hostilely, ignored, but really guys, why not just use fsl for your
customization needs? Colourizing output is in the cookbook:
http://fossil.0branch.com/fsl/wiki?name=Cookbook, along with lots of other
nifty tricks like aliasing, a
On Mon, Apr 25, 2016 at 4:48 PM, Michael Richter
wrote:
> I know that every time I mention this I get silently, perhaps even
> hostilely, ignored, but really guys, why not just use fsl for your
> customization needs? Colourizing output is in the cookbook:
> http://fossil.0branch.com/fsl/wiki?nam
On Mon, 25 Apr 2016 16:48:43 +0200, Michael Richter
wrote:
@michael: I have been using `fsl' myself happily for several years now. I
also have tried a couple of times to draw attention to its existence on
this list (getting the same feedback -- i.e.: none -- as you). but I am
sure you ar
On Apr 25, 2016, at 9:22 AM, Stephan Beal wrote:
>
>
> On Mon, Apr 25, 2016 at 4:48 PM, Michael Richter wrote:
> http://fossil.0branch.com/fsl/wiki?name=Cookbook,
> fwiw, i think you've misconstrued the conventional silence. i've always
> intended it as, "whew! We dodged that bullet again
On Mon, Apr 25, 2016 at 05:22:54PM +0200, Stephan Beal wrote:
> Yes, colorization is commonly-request feature, but is also not trivial to
> do portably, which is probably why relatively few people are interested in
> implementing it.
Uses terminfo is not that difficult and there are even separate
On Mon, Apr 25, 2016 at 5:33 PM, Steve Schow wrote:
> On Apr 25, 2016, at 9:22 AM, Stephan Beal wrote:
> Stephan…I’m new here. What do you mean by “dodged a bullet? Is fsl
> something to be afraid of for any reason?
>
No, quite the opposite: colorized output is a feature people keep asking
fo
On Mon, Apr 25, 2016 at 5:34 PM, Joerg Sonnenberger wrote:
> On Mon, Apr 25, 2016 at 05:22:54PM +0200, Stephan Beal wrote:
> > Yes, colorization is commonly-request feature, but is also not trivial to
> > do portably, which is probably why relatively few people are interested
> in
> > implementin
I’m new to fossil and thanks for pointing out this wrapper tool I’m going to
check it out for sure!
On Apr 25, 2016, at 8:48 AM, Michael Richter wrote:
> I know that every time I mention this I get silently, perhaps even hostilely,
> ignored, but really guys, why not just use fsl for your cu
On Mon, Apr 25, 2016 at 5:33 PM, Steve Schow wrote:
> On Apr 25, 2016, at 9:22 AM, Stephan Beal wrote:
>
> On Mon, Apr 25, 2016 at 4:48 PM, Michael Richter
> wrote:
>
>> http://fossil.0branch.com/fsl/wiki?name=Cookbook,
>>
> fwiw, i think you've misconstrued the conventional silence. i've alway
On Mon, 25 Apr 2016 18:03:27 +0200, Stephan Beal
wrote:
On Mon, Apr 25, 2016 at 5:33 PM, Steve Schow wrote:
On Apr 25, 2016, at 9:22 AM, Stephan Beal wrote:
On Mon, Apr 25, 2016 at 4:48 PM, Michael Richter
wrote:
http://fossil.0branch.com/fsl/wiki?name=Cookbook,
fwiw, i think you've
On Mon, Apr 25, 2016 at 6:42 PM, j. van den hoff
wrote:
> just for the record: `fsl' has been written by marc simpson (and he also
> still hosts the `fsl' repo). so (nearly or completely) all of the core
> functionality of `fsl' (as found on trunk) is due to him, I think. further
> tweaks/modific
I’m having trouble changing skins. It works on my local repo, but not on the
server repo.
1 - created repo on machine A. setup user foobar with s privs.
2 - created clone of that repo on machine B. also with user foobar with s
privs
3 - Working on the local machine B, I can run fossil ui,
On 4/25/16, Steve Schow wrote:
> I’m having trouble changing skins. It works on my local repo, but not on
> the server repo.
>
> 1 - created repo on machine A. setup user foobar with s privs.
>
> 2 - created clone of that repo on machine B. also with user foobar with s
> privs
>
> 3 - Working o
On 25 April 2016 05:33PM, j. van den hoff wrote:
> @michael: I have been using `fsl' myself happily for several years now. I
> also have tried a couple of times to draw attention to its existence on
> this list (getting the same feedback -- i.e.: none -- as you). but I am
> sure you are mistaken in
On Apr 25, 2016 8:48 AM, "Michael Richter" wrote:
>
> I know that every time I mention this I get silently, perhaps even
hostilely, ignored, but really guys, why not just use fsl for your
customization needs?
I don't use fsl myself, though I have no quarrel with its existence. I
think inferring h
On Mon, 25 Apr 2016, Michael Richter wrote:
I know that every time I mention this I get silently, perhaps even
hostilely, ignored, but really guys, why not just use fsl for your
customization needs? Colourizing output is in the cookbook:
http://fossil.0branch.com/fsl/wiki?name=Cookbook, along w
haven’t used that command yet at all. i wasn’t trying to copy skins from local
to server, I was just trying to login to the webui on the server and use it
directly through the webui. Go into admin section and hit the link for skins
and then there are install buttons for each of the skins you g
Hi Ron,
On 25 Apr 2016, at 09:08 , Ron W wrote:
> Push will push all content changes, including public check-ins, and wiki,
> ticket, and tech-note edits.
yeah, but that will only push changes into a repo having a common ancestor, no?
But what about if I want to put parts of a wiki into a compl
On 4/23/2016 5:06 PM, Marko Käning wrote:
On 24 Apr 2016, at 01:45 , John P. Rouillard wrote:
However once you had that info in the database, IIRC you can use th1 to
find out who the current user is. Then you can make sql calls into the
database. So I think in theory you could change/creat
I’ve understood now that
$ fossil config push skin
should actually push the clone’s skin to the central repo. :)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-use
Just to clarify, the fsl wrapper is not my work (although I contributed to
the cookbook and one of the standard enhancements in the default .fslrc
file was put in at my behest). I'm just a fan of DIY customization instead
of asking the core devs to add every little feature every user can think
of,
32 matches
Mail list logo
