From: Junio C Hamano <gitster@pobox.com>
To: Jan Durovec <jan.durovec@gmail.com>
Cc: git@vger.kernel.org, Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH] Adding list of p4 jobs to git commit message
Date: Fri, 15 Apr 2016 13:27:16 -0700 [thread overview]
Message-ID: <xmqq4mb2bot7.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <010201541b7a24b8-83b0f526-2f01-40e3-afc8-d81549af70d4-000000@eu-west-1.amazonses.com> (Jan Durovec's message of "Fri, 15 Apr 2016 19:51:10 +0000")
Jan Durovec <jan.durovec@gmail.com> writes:
> ---
A few issues. Please:
(1) Sign-off your work.
(2) Try to find those who are familiar with the area and Cc them.
"git shortlog -s -n --since=18.months --no-merges git-p4.py"
may help.
(3) Follow the style of existing commits when giving a title to
your patch.
"git shortlog --since=18.months --no-merges git-p4.py" may
help you notice "git-p4: do this thing" is the common way to
title "git p4" patches.
(4) Justify why your change is a good thing in your log message.
What you did, i.e. "list p4 jobs when making a commit", can be
seen by the patch, but readers cannot guess why you thought it
is a good idea to extract "job%d" out of the P4 commit and to
record them in the resulting Git commit, unless you explain
things like:
- what goes wrong if you don't?
- when would "job%d" appear in P4 commit?
- is it sane to assume "job0", "job1",... appear consecutively?
(5) Describe what your change does clearly. "Adding list" is not
quite clear. Where in the "git commit message" are you adding
the list, and why is that location in the message the most
appropriate place to add it?
Thanks.
> git-p4.py | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/git-p4.py b/git-p4.py
> index 527d44b..a81795f 100755
> --- a/git-p4.py
> +++ b/git-p4.py
> @@ -2320,6 +2320,15 @@ def extractFilesFromCommit(self, commit):
> fnum = fnum + 1
> return files
>
> + def extractJobsFromCommit(self, commit):
> + jobs = []
> + jnum = 0
> + while commit.has_key("job%s" % jnum):
> + job = commit["job%s" % jnum]
> + jobs.append(job)
> + jnum = jnum + 1
> + return jobs
> +
> def stripRepoPath(self, path, prefixes):
> """When streaming files, this is called to map a p4 depot path
> to where it should go in git. The prefixes are either
> @@ -2665,6 +2674,7 @@ def hasBranchPrefix(self, path):
> def commit(self, details, files, branch, parent = ""):
> epoch = details["time"]
> author = details["user"]
> + jobs = self.extractJobsFromCommit(details)
>
> if self.verbose:
> print('commit into {0}'.format(branch))
> @@ -2696,6 +2706,8 @@ def commit(self, details, files, branch, parent = ""):
> (','.join(self.branchPrefixes), details["change"]))
> if len(details['options']) > 0:
> self.gitStream.write(": options = %s" % details['options'])
> + if len(jobs) > 0:
> + self.gitStream.write(": jobs = %s" % (','.join(jobs)))
> self.gitStream.write("]\nEOT\n\n")
>
> if len(parent) > 0:
>
> --
> https://github.com/git/git/pull/225
next prev parent reply other threads:[~2016-04-15 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 19:51 [PATCH] Adding list of p4 jobs to git commit message Jan Durovec
2016-04-15 20:27 ` Junio C Hamano [this message]
2016-04-15 22:10 ` Luke Diamand
2016-04-16 13:46 ` Jan Durovec
2016-04-16 14:51 ` Lars Schneider
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=xmqq4mb2bot7.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jan.durovec@gmail.com \
--cc=luke@diamand.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.