 |
 |
The reason it works is that we never apply patches to a stable branch. All patches must come from maste; hence by implication they will always be carried forward. We've never had a problem with this approach. On Tue, 30 May 2017, Brian Bockelman wrote: > :) Maybe we work on a mutually-exclusive set of projects? Most of the ones I work on merge release branches through master as a mechanism to make sure patches in the stable series make it into the master branch. > > Regardless - I don't care too much provided we can have a written policy for branching and tagging that I can code against to provide the two items above. > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/pull/521#issuecomment-304894741 -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/521#issuecomment-304937666 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1