-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could supply an lxc container if requested
Am 07.08.2014 12:26, schrieb Cyril Brulebois:
While I haven't tried to reproduce this bug, the patch looks like
something that could indeed be merged.
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I could supply an lxc container if requested
Am 07.08.2014 12:26, schrieb Cyril Brulebois:
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iEYEARECAAYFAlPnXxAACgkQABMWRpwdNungEACgwCbt2IyhO/L08Sa7PyHchhqS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this bug is still valid with debbotstrap 1.0.48+deb7u1
is there any chance that this patch will be introduced or denied?
Cheers
B
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird -
Bjoern Boschman bjo...@boschman.de (2014-08-07):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this bug is still valid with debbotstrap 1.0.48+deb7u1
is there any chance that this patch will be introduced or denied?
While I haven't tried to reproduce this bug, the patch looks like
4 matches
Mail list logo