Hi,
I have 2 questions regarding fossil:
1) if I have 2 projects do I have to a) create 2 separate repositories
or do I b) put both source trees in one repository? if a), how do I run
fossil server to make both repositories accessible at the same time from
outside?
2) is it possible to deny
On Fri, Nov 04, 2011 at 11:31:26AM +0200, Zeev Pekar wrote:
1) if I have 2 projects do I have to a) create 2 separate repositories
or do I b) put both source trees in one repository? if a), how do I run
fossil server to make both repositories accessible at the same time from
outside?
Create
On 04.11.2011 11:45, Stephan Beal wrote:
@Everyone else: please correct that if it's wrong.
No need of correction, I use fossil this way too:
cat /etc/systemd/system/fossil.service
[Unit]
Description=Fossil Repositories
After=network.target
[Service]
Type=simple
User=fossil
Group=src
On Fri, Nov 4, 2011 at 12:25 PM, Zeev Pekar z.pe...@gmail.com wrote:
**
I do miss this feature... :( What is the best workaround for this today?
To use a DVCS which supports this. i'm not personally aware of any.
To developers: do you think this is important enough for you to implement
- Original message -
On Fri, Nov 4, 2011 at 12:25 PM, Zeev Pekar z.pe...@gmail.com wrote:
**
I do miss this feature... :( What is the best workaround for this
today?
To use a DVCS which supports this. i'm not personally aware of any.
gitolite supports ACL on paths if
On Fri, 04 Nov 2011 13:52:04 +0200
Zeev Pekar z.pe...@gmail.com wrote:
[...]
It would be impossible to implement within fossil's world view.
Once i clone a repo i have the whole thing, which i can then
manipulate (with admin-level rights) on my machine - you cannot
stop me from checking
On Fri, Nov 4, 2011 at 5:31 AM, Zeev Pekar z.pe...@gmail.com wrote:
2) is it possible to deny access to folders of the source tree to
certain users and grant access to the rest of the folders? (like in
gitolite)
With Fossil (or git or hg or mtn or bzr) each user has their own complete
copy
Hi folks,
I just ran into the following problem. I have a wiki page that is titled
DC Contact Sample. When I go through and browse from the home page, I
get the link http://127.0.0.1:8080/wiki?name=DC+-+Contact+%26amp%3B+Sample;
(i.e., I wrote [DC Contact Sample] in the wiki editor).
However,
On Fri, Nov 4, 2011 at 5:43 PM, Nolan Darilek no...@thewordnerd.infowrote:
some pushback from Git users. Is it possible to use Fossil in a workflow
with people who would rather use Git/Github?
Richard wrote a nice summary of that on Oct 16th which i'll paste in here:
---
Fossil
Thanks, but that's not really what I asked.
I totally get Fossil's development model, have used it for over a year
and think that it'd be a great fit for this particular community. I also
read this message when it was originally posted. But I may be working
with people who would rather submit
Hi Nolan, Stephan,
I think that this is doable for a restricted subclass of usage scenarios
(these conforming workflow style cited by Stephan above + bunch of
other restrictions).
We can benefit the fantastic opportunity of sqlite as fossil artifacts
container - I think that it is possible
On Fri, Nov 4, 2011 at 7:48 PM, Alek Paunov a...@declera.com wrote:
As Fossil API, for the proof of the concept, the server can use the JSON
API, Stephan ?
The biggest catch there is binary data, since JSON has no native way of
handing it. However, my current thinking on binary data is
On 04.11.2011 21:01, Stephan Beal wrote:
The biggest catch there is binary data, since JSON has no native way of
handing it. However, my current thinking on binary data is this...
from JSON we serve URL paths which, which called by an HTTP client, will
return the raw content (binary or not) for
Hi, all!
In a surprising (to me) turn of events:
http://www.fossil-scm.org/fossil/info/796dcfe072
the JSON API is now in the trunk and the json branch has been closed. The
JSON features are disabled by default and can be enabled by passing
--enable-json to the configure script. (Without
On 04.11.2011 22:32, Andreas Kupries wrote:
Does hg have something git's rebase and other history rewriting
operations ?
Yes - hg supports all of them and more (via various bundled [1] and
endless count of community extensions), but as you know, history
rewriting kills any repo/repo
Just a heads-up:
I did a quick test, and this didn't seem to work:
* Created a new Fossil repository
* Opened it into ./fossil, added README.txt with contents foo.
* Changed to parent directory, created Git repository in ./git
* Imported Fossil repo and switched to trunk branch
* Modified
On Fri, Nov 4, 2011 at 11:17 PM, Nolan Darilek no...@thewordnerd.infowrote:
Cool! Is it documented anywhere yet?
The current docs are in:
https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit
and are updated as the code is written.
As the API stabilizes the
17 matches
Mail list logo
