summaryrefslogtreecommitdiff
path: root/community/weblogs
diff options
context:
space:
mode:
authorArne Babenhauserheide <arne_bab@web.de>2009-07-22 01:02:01 +0200
committerArne Babenhauserheide <arne_bab@web.de>2009-07-22 01:02:01 +0200
commitaa633a336849b4888d6adb5256f6902c3f0682da (patch)
tree8a2c02c64c0df9310b49bf082385531a72c122b6 /community/weblogs
parent3b5d7be8e178bcfcd26174c53d3a69f083a88318 (diff)
Publish next news: Added info where to get the template (copy an older news entry).
Diffstat (limited to 'community/weblogs')
-rw-r--r--community/weblogs/ArneBab/howto-news-month-of-the-hurd.mdwn11
1 files changed, 10 insertions, 1 deletions
diff --git a/community/weblogs/ArneBab/howto-news-month-of-the-hurd.mdwn b/community/weblogs/ArneBab/howto-news-month-of-the-hurd.mdwn
index 7aa70337..17e6b6cb 100644
--- a/community/weblogs/ArneBab/howto-news-month-of-the-hurd.mdwn
+++ b/community/weblogs/ArneBab/howto-news-month-of-the-hurd.mdwn
@@ -18,7 +18,7 @@ For practical work that means, we use the following commands:
git fetch && git checkout -b master-news_next origin/master-news_next
-* get the latest version of news_next when you already created a local version
+* get the latest version of news_next when you already created a local version of the branch
git fetch && git checkout master-news_next
@@ -26,6 +26,15 @@ Always do check which branch you're on (asterisk in the first column of
``git branch'''s output), and only then begin to do your changes and
commit them.
+* create a new news entry
+
+ cp news/yyyy-mm-dd.mdwn news/YYYY-MM-DD.mdwn
+ (edit the new file)
+ git add news/YYYY-MM-DD.mdwn
+ git commit -m "Begun the news entry for YYYY-MM-DD."
+
+(just copy the most recent news file)
+
* check the outgoing changes
git log --reverse -p -C origin/master-news_next..master-news_next