2016-02-12 19:08 GMT+01:00 Radu Gheorghe <[email protected]>:
> Hello, > > I see that we now have a problem with the rsyslog-doc project that is > so nice to have :) And I need some help. > > Some of the PRs that come to > https://github.com/rsyslog/rsyslog-doc/pulls are related to new > features (neat, ha?). These have their own issues in the main rsyslog > repo and, being new, are not merged yet. The question is when should > we merge them. > > I suppose the obvious answer would be - when the feature issue from > the main repo is merged - we're good to go. After all, master docs > refer to master rsyslog. Would that work or do you have other > opinions? > I think this is the perfect way to do it. I usually try to have a look when I merge PRs if there are accompanying doc PRs, but I guess you have always been too fast ;) The real issue is how to detect that there actually is an acompanying PR in rsyslog... At least I think so... My 2 cts. Rainer > > I'm saying that this is a new problem because normally PRs come to fix > the existing docs. > > Thanks and best regards, > Radu > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > _______________________________________________ > 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. > _______________________________________________ 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.
