Excluded commits 2630fe1 and 8a6d7c0 which are new features.
@simonmichal, @abh3 Please let me know if there's anything else that should be removed (i.e. things that should wait for a 5.6 release). Given the number of commits, it may make sense to go for a feature release instead of a patch release, what do you think? In that case, for 5.6, I would like to try to merge the histories with git merge
such that the tag for v5.6.0 is actually in the linear history of the master branch, then stable-5.6.x
branches off of there. This is to make git describe
give more reasonable descriptions of commits on the master
branch (try git describe
on master
and stable-5.5.x
). When I rebase master on
the branch of this PR, I get the output below (compare with what current github/master
shows instead).
epsftws xrootd $ git describe master
v5.5.1-50-gf23a89ba9
epsftws xrootd $ git describe github/master
v5.2.0-99-osghotfix-TlsErrorHandling-947-g31a7f6c05
https://github.com/xrootd/xrootd/pull/1850
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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