On Sun, Dec 15, 2013 at 3:25 PM, Rainer Gerhards <[email protected]>wrote:
> Branches also make maintaining multiple versions really easy. I'll blog > tomorrow how i do it for rsyslog. > As promised, this is a description of my workflow: http://blog.gerhards.net/2013/12/how-i-maintain-multiple-rsyslog-versions.html It's *extremely* easy to mange the multiple versions. In spite of this, my recommendation to the doc project is a) create v5-stable, v7-stable, v7-devel, (master) branches b) import rsyslog v5-stable doc to v5-stable c) merge v5-stable to v7-stable (git pull . v5-stable) d) import rsyslog v7-stble doc to v7-stable; you now get a diff, commit that one e) merge v7-stabe to v7-devel f) import rsyslog v7-devel doc to v7-devel; you now get a diff, commit that one g) now it beomces a bit tricky, checkout master, delete evertyhign, commit (sorry....) h) merge v7-devel into master i) import rsyslog master doc to master; you now get a diff, commit that one At that point, you have the same structure that the main project has and you can now easily make doc updates using the described workflow. It's really worth it! I'd suggest to support v5-stable, even though it is outdated. Many distros ship it (even older versions...), so enhancements to it would definitely help improve rsyslog perception. Sorry again for not thinking enough in depth about it initially. As I said, I hand't expected we get such good results so quickly ;) @James, please let me know how you think you'll proceed, as this affects the way I contribute updates to the doc. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
