Perforce has an idea of a "job" and can connect changes to jobs
in order to connect code fixes to an external bug-tracking system,
for instance. The job can be specified in a change by adding
a section that looks like:
Jobs:
project-6032
For code committed from git p4, it would be nice to use a similar
notation in the commit message and have the jobs wind up in the
right section in the p4 change description.
This was discussed in
http://thread.gmane.org/gmane.comp.version-control.git/200445 .
These commits are on origin/next, as they depend on changes
in pw/git-p4-tests that was merged into next on Jul 3.
Pete Wyckoff (3):
git p4: remove unused P4Submit interactive setting
git p4 test: refactor marshal_dump
git p4: notice Jobs lines in git commit messages
git-p4.py | 188 ++++++++++++++++++++++++++---------------------
t/lib-git-p4.sh | 14 ++++
t/t9800-git-p4-basic.sh | 5 --
t/t9807-git-p4-submit.sh | 155 ++++++++++++++++++++++++++++++++++++++
4 files changed, 274 insertions(+), 88 deletions(-)
--
1.7.11.1.125.g4a65fea
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html