I can do that. However - smartass mode on - if one uses the actual "svn merge -c NNN,NNN", subversion will track that and
svn mergeinfo --show-revs merged ^/httpd/httpd/trunk . in a 2.4.x checkout will show it. But I am not trying to change existing practise here that works. And with pre-supplied 2.4 patches, this information might not be there - depends how it was created. -Stefan > Am 02.03.2016 um 15:05 schrieb Yann Ylavic <ylavic....@gmail.com>: > > On Wed, Mar 2, 2016 at 2:10 PM, <ic...@apache.org> wrote: >> Author: icing >> Date: Wed Mar 2 13:10:05 2016 >> New Revision: 1733279 >> >> URL: http://svn.apache.org/viewvc?rev=1733279&view=rev >> Log: >> backport > > We should try to reference the backported (trunk) revisions in the > commit messages. > Otherwise it could be hard later to figure which commit was backported > (or not), and we sometimes need to search by revision number (either > in revision logs, or even gg)...
