Re: Proper Merge Commit Format -- an announcement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > pt-tool indicates the destination branch, while github focuses on the
> > source branch. Is there a point in trying to have a more consistent way
> > of referring to the pull request ID and the branches involved?
> 
> It was a choice I made early on but not for any particular good
> reason. I don't really see a point in changing anything as the
> information about the source branch on Github is not particularly
> useful.

We have automated tooling (ceph-release-notes, backport-resolve-issue) that try 
to parse the PR merge commit messages. Having multiple formats does make that
job more difficult than it could be if only one format were used.

Nathan
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx



[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux