On Sat, 2005-10-08 at 21:06 +0200, Patrys :: Patryk Zawadzki wrote:
> Then if some people commit using trunk and some using general SPECS,
> such locks might become common.
There's no lock. The only situation where a post-commit commit might
fail, apart from a bug in the hook, is when there's a co
Dnia 08-10-2005, sob o godzinie 20:57 +0200, Paweł Sakowski napisał(a):
> On Sat, 2005-10-08 at 20:41 +0200, Patrys :: Patryk Zawadzki wrote:
> > > No, but the good thing is that nothing can get silently overwritten or
> > > sth -- I get a nice commit conflict. A superuser resolving those
> > > man
On Sat, 2005-10-08 at 20:41 +0200, Patrys :: Patryk Zawadzki wrote:
> > No, but the good thing is that nothing can get silently overwritten or
> > sth -- I get a nice commit conflict. A superuser resolving those
> > manually should be enough.
>
> Do we need superuser intervention in such cases?
W
Dnia 08-10-2005, sob o godzinie 20:21 +0200, Paweł Sakowski napisał(a):
> On Thu, 2005-09-29 at 23:08 +0200, Paweł Sakowski wrote:
> > I think it's possible to write a post-commit hook that would effectively
> > simulate a hardlink capability. [...]
> >
> > Does it sound like something that will k
On Thu, 2005-09-29 at 23:08 +0200, Paweł Sakowski wrote:
> I think it's possible to write a post-commit hook that would effectively
> simulate a hardlink capability. [...]
>
> Does it sound like something that will keep everybody happy?
Reasoning by the volume of replies I assume the answer is "y