in reply to PM Feature Idea: optionally add short comment on update

i also like the timestamp idea, like mentioned above by radiantmatrix.
what is common in other forum software that every update automatically generated a comment "Node updated by ... at 2005-...".
this way everybody will see that a node was updated and when.
  • Comment on Re: PM Feature Idea: optionally add short comment on update

Replies are listed 'Best First'.
Re^2: PM Feature Idea: optionally add short comment on update
by Happy-the-monk (Canon) on Sep 16, 2005 at 11:41 UTC

    Actually, users of the German language web board at Perl::Community.DE are used to that kind of qualifier.

    It has the limitation that only the latest edit is marked - and not what the change comprised of.

    Cheers, Sören

Re^2: PM Feature Idea: optionally add short comment on update
by halley (Prior) on Sep 16, 2005 at 15:56 UTC
    I don't like mandatory automatic stamps. I use preview for my initial posting and hit 'create' only when I think the response I give is useful, but I often go back and fine-tune it, rethink and improve it, and fix typos. If there were mandatory stamps, it would look like this.

    Updated (2005-16-09 11:50:23)

    Updated (2005-16-09 11:50:24)

    Updated (2005-16-09 11:50:31)

    Updated (2005-16-09 11:50:49)

    Updated (2005-16-09 11:52:51) Thanks for spotting that problem.

    Updated (2005-16-09 11:55:20)

    --
    [ e d @ h a l l e y . c c ]

      it would look like this.
      who said that?
      it could just show the last update in a small font. at least it's like that at perl-community.de, for example.
      i would really like to see if someone updated their node silently. their could also be a minimum of time, so that, if you update up to, say 3 minutes after posting because of a typo, there would be no mandatory stamp.

      As tinita already said, the 'fixing of typos' a couple of minutes after the original post would not be marked.

      Then, some more minutes later, only the last edit would be automagically marked, and by whom the edit was (could well have been a janitor).
      Thus all you'd ever see was that the node was later edited (i.e. not exactly in the state it was in when first written).

      This puts just a little pressure on authors/editors to sometimes note what they've changed - and why.

      Cheers, Sören