On Wed, Apr 3, 2013 at 5:55 AM, Matt Welland estifo...@gmail.com wrote:
2. Adding branch name pattern filtering to sync.
if i'm not sorely mistaken, one of the contributors started work on
branch-specific syncing at some point, but i don't know how far along he
got. Maybe he'll read this and
On 3/30/13, Stephan Beal sgb...@googlemail.com wrote:
Fossil _repos_ are indeed intended to be used by relatively few people at a
time. Fossil is designed for small, relatively tight-knit teams. It does
not directly support deep hierarchies of developers like git does.
From my limited
On 03/30/2013 02:59 AM, Stephan Beal wrote:
On Sat, Mar 30, 2013 at 4:06 AM, Steve Havelka yo...@q7.com
mailto:yo...@q7.com wrote:
You're saying that Fossil is intended to be used by few people, or
that
Fossil is intended not to have a user community?
Fossil _repos_ are
On Tue, Apr 2, 2013 at 4:12 PM, Steve Havelka yo...@q7.com wrote:
On 03/30/2013 02:59 AM, Stephan Beal wrote:
On Sat, Mar 30, 2013 at 4:06 AM, Steve Havelka yo...@q7.com wrote:
You're saying that Fossil is intended to be used by few people, or that
Fossil is intended not to have a user
On Sat, Mar 30, 2013 at 4:06 AM, Steve Havelka yo...@q7.com wrote:
You're saying that Fossil is intended to be used by few people, or that
Fossil is intended not to have a user community?
Fossil _repos_ are indeed intended to be used by relatively few people at a
time. Fossil is designed for
Just wondering why we need a dedicated fossil hosting service.
I have managed for years without.
For example: Copy fossil repository to dropbox folder; make folder
publicly available, or privately share it. Done!
Am I missing something?
James
On 03/29/2013 09:29 AM, James Bremner wrote:
Just wondering why we need a dedicated fossil hosting service.
I have managed for years without.
For example: Copy fossil repository to dropbox folder; make folder
publicly available, or privately share it. Done!
Am I missing something?
On Fri, Mar 29, 2013 at 12:29 PM, James Bremner ja...@ravenspoint.comwrote:
Copy fossil repository to dropbox folder; make folder publicly available,
or privately share it. Done!
Huh. Very clever!
But surely this technique should at least be documented, right?
--
D. Richard Hipp
A snag with using dropbox, or similar, as a replacement for a dedicated
fossil server has occurred to me.
When a person interacts with the repo, fossil will update the local copy
of the repo and then dropbox will synchronize all the different local
copies. On a busy repo where there might be
On Fri, Mar 29, 2013 at 5:33 PM, Steve Havelka yo...@q7.com wrote:
Hmm...could I clone a repository directly from your Dropbox-hosted one?
Or push changes back to it?
This works to some degree (i've done it before) but breaks down if one or
more of the clients involved is offline for any
for what it's worth as compared to github you are missing:
Ability to browse and discover projects based on searches, tags and
developer.
Ability for loosely coupled collaboration (i.e. fork).
Community and the momentum that can come with it.
Project life beyond the initial developer.
On
Matt Welland decía, en el mensaje Re: [fossil-users] Why do we need a fossil
hosting service? del Viernes, 29 de Marzo de 2013 14:38:25:
Ability for loosely coupled collaboration (i.e. fork).
Not exactly what Fossil was designed for, I believe...
Community and the momentum that can come
On 03/29/2013 05:56 PM, Richie Adler wrote:
Matt Welland decía, en el mensaje Re: [fossil-users] Why do we need a fossil
hosting service? del Viernes, 29 de Marzo de 2013 14:38:25:
Ability for loosely coupled collaboration (i.e. fork).
Not exactly what Fossil was designed for, I believe
13 matches
Mail list logo
