Skip to content

Commit 697d7da

Browse files
committed
fixing formatting issues on backport guidelines
1 parent fa635cb commit 697d7da

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

Developer-guide/Backport Guidelines.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,13 @@ that do not apply cleanly will need some manual modifications and using
2323
3. Cherry pick the change from master.
2424

2525
$ git cherry-pick -x a0b1c2d3e4f5
26-
2726
- verify that the change has been merged in the master branch.
2827

2928
4. Update/correct the commit message.
3029

3130
$ git commit -s --amend --date="$(date)"
3231

3332
[This is one example](https://github.com/gluster/glusterfs/commit/40407afb529f6e5fa2f79e9778c2f527122d75eb) of the commit message that has a good description for a backport. Notice the indention of the patch-metadata like BUG, Change-ID and Reviewed-on tags. There is also the original commit-id that was cherry picked from the master branch.
34-
3533
- make sure to quote the review tags
3634
- update the BUG reference, point to the BUG that is used for this
3735
particular release-branch

0 commit comments

Comments
 (0)