* Petter Reinholdtsen ([EMAIL PROTECTED]) [061211 10:27]:
> [Steve Langasek]
> > Does this mean you think sysvinit -36 in unstable is not quite ready
> > for release, and that we should be looking at t-p-u for a solution
> > to bug #330592? Or should we be considering the unstable version
> > for
[Steve Langasek]
> Does this mean you think sysvinit -36 in unstable is not quite ready
> for release, and that we should be looking at t-p-u for a solution
> to bug #330592? Or should we be considering the unstable version
> for inclusion now?
Hm, right. I guess I was not too clear. I will try
Hi Petter,
On Sun, Nov 26, 2006 at 08:49:38PM +0100, Petter Reinholdtsen wrote:
> > I fear I missed your answer on that mail - in case we want to push
> > the new sysvinit to testing, this needs to happen quite fast.
> Yes. I fear we will be to late, as some issues are still not properly
> solve
I'm sorry for answering so late, but the reason is simply that I did
not know what to answer. It has been a while since I worked on
sysvinit the last time, and the remaining issues have been rather hard
to find a solution for. This weekend I managed to sit down and have a
look at the issues.
> I
Hi,
* Petter Reinholdtsen ([EMAIL PROTECTED]) [061021 15:48]:
> As you probably are aware, only part of my work on sysvinit made it
> into Etch. I am still not sure if I should request an exception from
> the release team to get an updated version into Etch or not. On one
> hand, I would like t
As you probably are aware, only part of my work on sysvinit made it
into Etch. I am still not sure if I should request an exception from
the release team to get an updated version into Etch or not. On one
hand, I would like to have some features in Etch, and on the other
hand, there are some uns
6 matches
Mail list logo