Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes:
> ... Note that the single boundary test is empirical, not
> theoretical; even a -2 limiting condition will give a diffstat if there's
> only one boundary commit in this particular case.
It is unclear what "a -2 limiting condition" means here...
> @@ -679,21 +682,19 @@ static void make_cover_letter(struct rev_info *rev,
>
> strbuf_release(&sb);
>
> + shortlog_init(&log);
> + for (i = 0; i < nr; i++)
> + shortlog_add_commit(&log, list[i]);
> +
> + shortlog_output(&log);
> +
Nice ;-)
> @@ -962,7 +957,15 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
>
> if (prepare_revision_walk(&rev))
> die("revision walk setup failed");
> + rev.boundary = 1;
> while ((commit = get_revision(&rev)) != NULL) {
> + if (commit->object.flags & BOUNDARY) {
> + fprintf(stderr, "Boundary %s\n", sha1_to_hex(commit->object.sha1));
Leftover debugging?
-
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
