Larry D'Anna <larry@xxxxxxxxxxxxxx> writes:
> If --porcelain is used git-push will produce machine-readable output. The
> output status line for each ref will be tab-separated and sent to stdout instead
> of stderr. The full symbolic names of the refs will be given. For example
>
> $ git push --dry-run --porcelain master :foobar 2>/dev/null \
> | perl -pe 's/\t/ TAB /g'
>
> = TAB refs/heads/master:refs/heads/master TAB [up to date]
> - TAB :refs/heads/foobar TAB [deleted]
> ---
Thanks. Sign-off?
On a tangent, this reminds me of something that I often find myself
wanting to do. Currently I do:
$ git push --dry-run
A..B master -> master
$ git log --oneline A..B ;# cut and paste A..B from the output
$ git push
to achieve what I want; get an overview of what I'd be pushing as the
final sanity check before running the actual push.
I've been wondering if it would be a good idea to teach -v (or some other
option) to do this automatically. That is,
$ git push [--dry-run] [--summary[=<n>]]
would give the output from "git log --oneline [-n <n>] A..B".
No, I am not suggesting you to fold such an unrelated feature to your
patch at all.
--
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