On Mon, Jul 11, 2011 at 01:29:52PM -0400, Rice, James M CIV NSWCDD, K73 wrote:
> Restating the problem. I wish for our developers to be able to
> reference multiple commits with one number, and then find those
> commits via that number. And I don't mind scripting to accomplish
> this. I know, that CR # can be put in the commit message, then I can
> grep and parse the log, that is the hard way.
There are two ways to approach this: tell the CM tool about some git
commits, or tell some git commits about the CR number.
For telling the CM tool about git commits, refer to them by their sha1
commit ids. If the commits are sequential, you can refer to the
sequence by its endpoints. And then if you want to know which files were
touched, you can just diff the endpoints, like:
$ git diff-tree --name-only $start $end
It's not a number, exactly, but it is a fixed size (two 40-byte commit
ids). Would that work in your CM tool?
If the commits aren't sequential, you can do something similar, but you
have a variable-length list of commit ids, and you get the set of
changed files like:
$ for i in $commits; do
git diff-tree --name-only $i |
tail -n +2
done | sort -u
If you want to do the reverse and tell git about CR numbers, then I
don't think you have much option besides putting them in the commit
message. Which means you'll need to grep to get them out. You can do
something like:
$ git log --grep='CR#' --pretty=format: --name-only
-Peff
--
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