Skip to main content
Server Fault

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Pythonone for Python was (re)closed.

The majority of their "big" hidden features questionshidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

The m.SO questionm.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

Fixup of bad MSO links to MSE links migration
Source Link
Community Bot
Community Bot
  • 1

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features""hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big""big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

The m.SO question posted by Mark is from July of last year; in October of last year, a number of SO's "hidden features" questions were closed and locked - and even as recently as a week ago, the one for Python was (re)closed.

The majority of their "big" hidden features questions seem to be closed and/or locked, but some are not; it doesn't seem to be quite a settled debate.

But, hey: we're not Stack Overflow, and I think we can make this one idiosyncrasy that we choose not to inherit.

Migration of MSO links to MSE links
Source Link
Community Bot
Community Bot
  • 1
Source Link
Shane Madden
Shane Madden
  • 115.9k
  • 17
  • 31