On Wed, Oct 19, 2011 at 07:41:56PM +0200, Stephan Beal wrote:
>> That could even help even before fossil having a capability of
>> centraliising locks; the read-only permissions could be enough for
>> the people in a team to decide on the locks.
> Can we do read-only cross-platform (i.e. Windows)?
On Wed, Oct 19, 2011 at 10:50:05AM -0700, Mike Meyer wrote:
> 2011/10/19 Lluís Batlle i Rossell
>
> No, I take that back. You could force locking to use a central server model.
> For each repository, you have to set a repository as the "lock server".
> Using "self" or some such would mean "You ar
2011/10/19 Lluís Batlle i Rossell
> On Wed, Oct 19, 2011 at 09:38:44AM -0700, Mike Meyer wrote:
> > This requires a lot of work on fossils part in order to be reliable.
> If I had to implement that on fossil, I'd use some kind of table like the
> shun
> table, propagated on autosync, that would b
2011/10/19 Lluís Batlle i Rossell
> Well, the tags name or value could have the file name.
>
That's an idea. But we would also need the branch, wouldn't we? Or does the
tag follow the branch?
> Maybe, instead of tags, there could be a list like the versionable
> 'glob-ignore', of files that re
On Wed, Oct 19, 2011 at 07:27:56PM +0200, Stephan Beal wrote:
> 2011/10/19 Lluís Batlle i Rossell
>
> > the file, and that also has only an informative role. Maybe something like
> > propagated tags could mark files as needs_lock, and act accordingly on
> > updates/checkouts/...
> >
>
> You foun
2011/10/19 Lluís Batlle i Rossell
> the file, and that also has only an informative role. Maybe something like
> propagated tags could mark files as needs_lock, and act accordingly on
> updates/checkouts/...
>
You found another use for propagating tags ;).
As someone pointed out the original th
On Wed, Oct 19, 2011 at 09:38:44AM -0700, Mike Meyer wrote:
> This requires a lot of work on fossils part in order to be reliable. Unlike
> source changes, you can't do a commit and then require a merge before
> pushing if there's a collision. There are also nasty restrictions on how you
> do thing
This requires a lot of work on fossils part in order to be reliable. Unlike
source changes, you can't do a commit and then require a merge before
pushing if there's a collision. There are also nasty restrictions on how you
do things. In particular, you have to have autosync on (or ignore it if off)
8 matches
Mail list logo
