On Saturday 18 January 2014 19:21:11 Alexander Berntsen wrote:
Rename --autounmask-write to --autounmask.
typically when we delete/rename an option, we give users a heads up. that
means a cycle where the old option exists but emits a warning before switching
to the new one. then we can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/01/14 10:20, Mike Frysinger wrote:
typically when we delete/rename an option, we give users a heads
up. that means a cycle where the old option exists but emits a
warning before switching to the new one. then we can delete it.
We should
On Sunday 19 January 2014 05:48:33 Alexander Berntsen wrote:
On 19/01/14 10:20, Mike Frysinger wrote:
typically when we delete/rename an option, we give users a heads
up. that means a cycle where the old option exists but emits a
warning before switching to the new one. then we can delete
Rename --autounmask-write to --autounmask. Please note that removing the
option does not mean that the variable used for keeping track of
autounmask writing is not removed from depgraph.py.
---
man/emerge.1| 19 +++
pym/_emerge/depgraph.py | 4 ++--
On Sat, Jan 18, 2014 at 7:21 PM, Alexander Berntsen
alexan...@plaimi.net wrote:
Rename --autounmask-write to --autounmask. Please note that removing the
option does not mean that the variable used for keeping track of
autounmask writing is not removed from depgraph.py.
Ok, so how do I tell
