projects / platform / upstream / perl.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 15a4d87) | patch
RMG - Add a note about merging the release branch back into blead
authorSteve Hay <steve.m.hay@googlemail.com>
Sat, 21 Sep 2013 00:05:11 +0000 (01:05 +0100)
committerSteve Hay <steve.m.hay@googlemail.com>
Sat, 21 Sep 2013 00:05:11 +0000 (01:05 +0100)
commit121e9ff07b1fa7db2551baae0acbd44955c0ea1d
tree859e553d46cc45968482368f4b55e11ced881887tree | snapshot
parent15a4d87479c14a0808c36a762bcd182890b84815commit | diff
RMG - Add a note about merging the release branch back into blead

I was momentarily confused and almost did the wrong thing when I saw that
"git merge release-5.19.4" had produced a merge commit (71d5a36340),
whereas the merge of 5.19.3 a month ago did not (see f865d60069).

The cause was simply that a change (ac239e1c3e) had been pushed to blead
since I'd created the release branch, which had not happened when merging
the 5.19.3 release branch last month.
Porting/release_managers_guide.pod diff | blob | history
Domain: System / Base;