Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Ask them to put it in a new post?
On 2009-06-09, Austin English austinenglish@gmail.com wrote:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
-- -Austin
On Mon, Jun 8, 2009 at 5:23 PM, Ben Kleinshacklein@gmail.com wrote:
Ask them to put it in a new post?
On 2009-06-09, Austin English austinenglish@gmail.com wrote:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
While we could do that, that would require doing so for just about every post that is made on wine-users, which is a bit ridiculous.
On Mon, 8 Jun 2009 14:41:57 -0500 Austin English austinenglish@gmail.com wrote:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
+1 It's not quite as big a problem for those of us who use the forum, but if people don't mark their post as edited, it's not necessarily obvious even to us that something has been changed. Edits just cause problems, with no significant benefit that I can think of.
2009/6/9 Austin English austinenglish@gmail.com:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Maybe just add notice on edit page stating that edits are for minor changes only, and if one has some additional information he should add it as a separate post?
On Mon, Jun 8, 2009 at 10:40 PM, Igor Tarasovtarasov.igor@gmail.com wrote:
2009/6/9 Austin English austinenglish@gmail.com:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Maybe just add notice on edit page stating that edits are for minor changes only, and if one has some additional information he should add it as a separate post?
I don't think the minor benefits of edits outweigh the downsides. 'Minor changes' is subject to interpretation, and we all know how that ends...
"Igor Tarasov" tarasov.igor@gmail.com wrote:
2009/6/9 Austin English austinenglish@gmail.com:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Maybe just add notice on edit page stating that edits are for minor changes only, and if one has some additional information he should add it as a separate post?
There is a request to not paste logs and backtraces when adding a comment to a bug, that doesn't prevent that very well. So disabling the feature is always a preference.
On Mon, Jun 8, 2009 at 11:12 PM, Dmitry Timoshkovdmitry@codeweavers.com wrote:
"Igor Tarasov" tarasov.igor@gmail.com wrote:
2009/6/9 Austin English austinenglish@gmail.com:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Maybe just add notice on edit page stating that edits are for minor changes only, and if one has some additional information he should add it as a separate post?
There is a request to not paste logs and backtraces when adding a comment to a bug, that doesn't prevent that very well. So disabling the feature is always a preference.
Jeremy, would you mind disabling edits please?
Editing disabled.
-Newman
Austin English wrote:
On Mon, Jun 8, 2009 at 11:12 PM, Dmitry Timoshkovdmitry@codeweavers.com wrote:
"Igor Tarasov" tarasov.igor@gmail.com wrote:
2009/6/9 Austin English austinenglish@gmail.com:
Users are editing their posts when asked for terminal output/wine version/etc. Those of us on the mailing list side don't get this information.
Maybe just add notice on edit page stating that edits are for minor changes only, and if one has some additional information he should add it as a separate post?
There is a request to not paste logs and backtraces when adding a comment to a bug, that doesn't prevent that very well. So disabling the feature is always a preference.
Jeremy, would you mind disabling edits please?
On Fri, Jun 12, 2009 at 12:51 PM, Jeremy Newmanjnewman@codeweavers.com wrote:
Editing disabled.
-Newman
Thanks!