git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: git@vger.kernel.org
Cc: Michael Horowitz <mike@horowitz.name>
Subject: [PATCH 0/3] git p4: notice Jobs: section in submit
Date: Wed,  4 Jul 2012 09:34:17 -0400	[thread overview]
Message-ID: <1341408860-26965-1-git-send-email-pw@padd.com> (raw)

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

             reply	other threads:[~2012-07-04 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 13:34 Pete Wyckoff [this message]
2012-07-04 13:34 ` [PATCH 1/3] git p4: remove unused P4Submit interactive setting Pete Wyckoff
2012-07-04 13:49   ` Pete Wyckoff
2012-07-05  7:20   ` Luke Diamand
2012-07-05 12:30     ` Pete Wyckoff
2012-07-14 13:53       ` Pete Wyckoff
2012-07-04 13:34 ` [PATCH 2/3] git p4 test: refactor marshal_dump Pete Wyckoff
2012-07-04 13:34 ` [PATCH 3/3] git p4: notice Jobs lines in git commit messages Pete Wyckoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1341408860-26965-1-git-send-email-pw@padd.com \
    --to=pw@padd.com \
    --cc=git@vger.kernel.org \
    --cc=mike@horowitz.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).