From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tay Ray Chuan <rctay89@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Larry D'Anna <larry@elder-gods.org>
Subject: Re: Suggestion on git-push --porcelain
Date: Tue, 9 Feb 2010 23:54:46 -0500 [thread overview]
Message-ID: <20100210045446.GC28526@coredump.intra.peff.net> (raw)
In-Reply-To: <7vmxzhn6fp.fsf@alter.siamese.dyndns.org>
On Tue, Feb 09, 2010 at 06:57:46PM -0800, Junio C Hamano wrote:
> Tay Ray Chuan <rctay89@gmail.com> writes:
>
> > $ git push --porcelain
> > PORCELAIN To git://foo.com/git/myrepo.git
> > PORCELAIN uptodate refs/heads/baz:refs/heads/baz 1234ab ba4321
> > PORCELAIN nonff refs/heads/bar:refs/heads/bar 2345cd 3456de
> >
> > This is an "positive" approach, in the sense that we don't remove
> > anything from the current output; we just add more printf("PORCELAIN")
> > lines to wherever is appropriate.
>
> Sorry, but I don't see what that would solve. For example, we used not to
> give the destination to the standard output stream, but that line carries
> a necessary information and Larry's series corrects that.
I think he is trying to future-proof any additional output that push (or
remote helpers) produce. I don't think it is really worth it, though.
All of that should be going to stderr, and thus would be, at worst,
noise on the terminal. I don't think it is that hard or error-prone a
rule to send such cruft to stderr.
-Peff
next prev parent reply other threads:[~2010-02-10 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 2:34 Suggestion on git-push --porcelain Tay Ray Chuan
2010-02-10 2:57 ` Junio C Hamano
2010-02-10 4:54 ` Jeff King [this message]
2010-02-10 11:28 ` Tay Ray Chuan
2010-02-10 11:18 ` Tay Ray Chuan
2010-02-10 19:14 ` Junio C Hamano
2010-02-10 3:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100210045446.GC28526@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larry@elder-gods.org \
--cc=rctay89@gmail.com \
/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 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 NNTP newsgroup(s).