summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://dmarti.myopenid.com/ <http://dmarti.myopenid.com/@web>2008-09-12 08:50:13 -0400
committerJoey Hess <joey@kitenet.net>2008-09-12 08:50:13 -0400
commit568deafab6d6de44b2dc6cb672b49c7d4b278f81 (patch)
tree0ed2406f981f2e63c94a0728d81b8fce367b8cc0
parentead3c9caa4eed98efd74ea6bdb46dacb72d7074f (diff)
-rw-r--r--doc/todo/tagging_with_a_publication_date.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/todo/tagging_with_a_publication_date.mdwn b/doc/todo/tagging_with_a_publication_date.mdwn
index 8c20760ab..18c8b712c 100644
--- a/doc/todo/tagging_with_a_publication_date.mdwn
+++ b/doc/todo/tagging_with_a_publication_date.mdwn
@@ -22,3 +22,16 @@ on vacation".
> pages. Alternatively, for larger organisations wishing to deploy more
> sweeping changes on a given date, replace cron job with intern.. ;-)
> --[[Joey]]
+
+> > Good approach if you have one day on which a big change goes through, but
+> > often the reason for tagging with a publication date is so that you can
+> > dribble out articles one per day when you're gone for a week. Branches are easy
+> > in git, but it would still be an extra step to switch branches every time
+> > you edit a different day's article.
+> >
+> > And just to make it a little harder, some sites might want an internal
+> > copy of the wiki that _does_ build the future pages, just tags them with the publication
+> > date, for previewing.
+> >
+> > I no longer have the original wiki for which I wanted this feature, but I can
+> > see using it on future ones. -- [[DonMarti]]