On Wed, May 27, 2015 at 3:06 PM, j. van den hoff
wrote:
> On Wed, 27 May 2015 19:24:38 +0200, Ron W wrote:
>>
>> On Wed, May 27, 2015 at 6:10 AM, j. van den hoff <
>> veedeeh...@googlemail.com>
>> wrote:
>>
>> the "request to work on branch" is the catch: he wants to ensure that
>>> students ca
On Wed, 27 May 2015 19:24:38 +0200, Ron W wrote:
(Sorry, accidently clicked the "Send" button when trying to click the
"unfold" icon in the editor.)
On Wed, May 27, 2015 at 6:10 AM, j. van den hoff
wrote:
the "request to work on branch" is the catch: he wants to ensure that
students can
On Wed, 27 May 2015 18:49:46 +0200, David Mason wrote:
I use Fossil in 2 ways with students.
1) for each research project I have a Fossil, and all Grad students
working
on that project (and I) have commit access. There are few enough people
that it works out.
I think that's what my colle
On Wed, 27 May 2015 18:05:15 +0200, Andy Bradford
wrote:
Thus said "j. van den hoff" on Wed, 27 May 2015 12:10:57 +0200:
the "request to work on branch" is the catch: he wants to ensure that
students can never mess up trunk, i.e. must technically not be able to
merge anything into trunk.
On Wed, May 27, 2015 at 8:01 AM, Martin Gagnon wrote:
>
> I wonder if it would be a good idea to implement a new feature that
> would be half way between per-branch push permission and emailing
> bundles ?
>
I am wondering if there's a way to do a pull in such a way that it could be
"purged" simi
On Wed, 27 May 2015 08:01:54 -0400
Martin Gagnon wrote:
> On Wed, May 27, 2015 at 07:25:43AM -0400, Richard Hipp wrote:
> > On 5/27/15, j. van den hoff wrote:
> > > he wants to ensure that
> > > students can never mess up trunk, i.e. must technically not be able to
> > > merge anything into trun
Yes, I asked about this in another thread. Can we use TH1 to color the
Timeline entries per User?
On Wed, May 27, 2015 at 1:30 PM, Ron W wrote:
> On Wed, May 27, 2015 at 7:25 AM, Richard Hipp wrote:
>
>> Fossil provides capabilities that make
>> it trival for the instructor to see that a studen
On Wed, May 27, 2015 at 7:25 AM, Richard Hipp wrote:
> Fossil provides capabilities that make
> it trival for the instructor to see that a student has pushed to
> trunk
It would be even more trivial to see such pushes if fossil time line could
color the user names in the timeline display. Even
(Sorry, accidently clicked the "Send" button when trying to click the
"unfold" icon in the editor.)
On Wed, May 27, 2015 at 6:10 AM, j. van den hoff
wrote:
> the "request to work on branch" is the catch: he wants to ensure that
> students can never mess up trunk
You could achieve a "safety net
On Wed, May 27, 2015 at 6:10 AM, j. van den hoff
wrote:
> a colleague is considering to use fossil in a setup where he (the group
> leader) supervises several students having dedicated tasks within a larger
> project. what he would like to do is
>
> * set up master repo
>
> * give student(s) clon
On Wed, May 27, 2015 at 7:25 AM, Richard Hipp wrote:
> The other approach would be to deny "push" privileges to the students
> and force them to email in "bundles" that contain their changes, to be
> added back to the trunk administratively by the instructor. That's a
> lot more work on the inst
I use Fossil in 2 ways with students.
1) for each research project I have a Fossil, and all Grad students working
on that project (and I) have commit access. There are few enough people
that it works out.
2) for assignments, I create a Fossil per student and the student plus the
marker(s) and I
Thus said "j. van den hoff" on Wed, 27 May 2015 12:10:57 +0200:
> the "request to work on branch" is the catch: he wants to ensure that
> students can never mess up trunk, i.e. must technically not be able to
> merge anything into trunk.
Trunk in *which* clone of the repository? Perhaps the
On Wed, 27 May 2015 13:25:43 +0200, Richard Hipp wrote:
On 5/27/15, j. van den hoff wrote:
he wants to ensure that
students can never mess up trunk, i.e. must technically not be able to
merge anything into trunk.
When the students have a copy of the repo on their local machine, they
can ove
On Wed, May 27, 2015 at 07:25:43AM -0400, Richard Hipp wrote:
> On 5/27/15, j. van den hoff wrote:
> > he wants to ensure that
> > students can never mess up trunk, i.e. must technically not be able to
> > merge anything into trunk.
...
>
> The other approach would be to deny "push" privileg
On 5/27/15, j. van den hoff wrote:
> he wants to ensure that
> students can never mess up trunk, i.e. must technically not be able to
> merge anything into trunk.
When the students have a copy of the repo on their local machine, they
can override any permissions that anybody sets up and do absolu
a colleague is considering to use fossil in a setup where he (the group
leader) supervises several students having dedicated tasks within a larger
project. what he would like to do is
* set up master repo
* give student(s) clone/pull/push permisisons for the repo
* require student(s) to bra
17 matches
Mail list logo
