Hi,
On Tue, 26 Aug 2014, Cyril Brulebois wrote:
> I might be misremembering of course but I think d-i on linux archs has
> been working more or less during the whole release cycle. (The parted
I can confirm this as I imported d-i snapshots from git into Kali to cope
with new upstream kernels that
Steven Chamberlain (2014-08-25):
> On 25/08/14 04:55, Cyril Brulebois wrote:
> > * Architecture support: my own, limited testing made me discover how
> >badly broken d-i on GNU/kFreeBSD was, and I shared my concerns some
> >days ago with BSD people and the release team. I haven't seen any
On 25/08/14 04:55, Cyril Brulebois wrote:
> * Architecture support: my own, limited testing made me discover how
>badly broken d-i on GNU/kFreeBSD was, and I shared my concerns some
>days ago with BSD people and the release team. I haven't seen anyone
>commit to fixing d-i there and ma
Hi,
Just a question: can we provide d-i update asynchronously with
release? It means, should we put all thing with Jessie and
postpone delayed items until Jessie+1? Is there any way to provide
nice features without stable release? Does "Regular releases" mean
"until Jessie release" or "every
Hi,
since Steve asked me whether I had some stuff to share for the upcoming
Debian installer and CD BoF at DebConf, here are a few things dug from
my d-i todo list (without any kind of prioritization). In brackets, the
status/impact for jessie.
Since it's almost 6am locally, I hope you won't hate
5 matches
Mail list logo
