From: Junio C Hamano <gitster@pobox.com>
To: Larry D'Anna <larry@elder-gods.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] add --porcelain option to git-push
Date: Thu, 25 Jun 2009 12:07:08 -0700 [thread overview]
Message-ID: <7vtz249lpf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20090623011001.GA15352@cthulhu> (Larry D'Anna's message of "Mon\, 22 Jun 2009 21\:10\:01 -0400")
Larry D'Anna <larry@elder-gods.org> 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.
next prev parent reply other threads:[~2009-06-25 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 21:28 I'd like to be able to know what git-push will do Larry D'Anna
2009-06-22 21:40 ` Jeff King
2009-06-23 1:10 ` [PATCH] add --porcelain option to git-push Larry D'Anna
2009-06-23 15:07 ` Marc Branchaud
2009-06-23 15:38 ` [PATCH] add --plumbing " Larry D'Anna
2009-06-23 15:50 ` [PATCH] add --porcelain " Junio C Hamano
2009-06-23 17:09 ` Marc Branchaud
2009-06-23 18:41 ` Markus Heidelberg
2009-06-23 22:38 ` Constantine Plotnikov
2009-06-24 0:26 ` Larry D'Anna
2009-06-25 19:07 ` Junio C Hamano [this message]
2009-06-25 19:30 ` Larry D'Anna
2009-06-27 0:23 ` [PATCH] add --summary " Larry D'Anna
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtz249lpf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=larry@elder-gods.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).