[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Atomic file locking update
From: |
Svante Signell |
Subject: |
Re: Atomic file locking update |
Date: |
Thu, 27 Nov 2014 19:25:54 +0100 |
On Thu, 2014-11-27 at 15:56 +0100, Samuel Thibault wrote:
> Svante Signell, le Thu 27 Nov 2014 13:49:53 +0100, a écrit :
> As discussed on IRC too, AIUI the record locking patches just get rid
> of the whole content that I'm patching. So the rebase should be quite
> trivial: just tell git to keep your version.
I don't use git. I use released versions and debian+quilt+manual patch
management.
> > On the other hand, I've been running at least 5 VMs
> > with these patches since August without problems.
>
> But were you running applications which were actually using record
> locking? Few applications use locks at all, actually :)
Well at lest all applications using whole file locking, such as dpkg
runs with the record file locking structures, not using lockf or LOCK_*
anymore.
> > Of course these patches ar not up to GCS standards, so let's forget
> > about the whole issue. I continue to rebase and apply them privately
> > for every hurd/libc release to come.
>
> I'm not sure to understand what you mean here.
That I keep the patches for myself of course, and don't publish them.