From: Tay Ray Chuan <rctay89@gmail.com>
To: "Larry D'Anna" <larry@elder-gods.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] git-push: make git push --porcelain print "Done"
Date: Sat, 27 Feb 2010 12:19:20 +0800 [thread overview]
Message-ID: <be6fef0d1002262019j2088d20dp89f1587e3921a1ba@mail.gmail.com> (raw)
In-Reply-To: <04fc63d0f8114f0cd721bcf3dff1f108e30b5308.1267243044.git.larry@elder-gods.org>
Hi,
On Sat, Feb 27, 2010 at 11:59 AM, Larry D'Anna <larry@elder-gods.org> wrote:
> diff --git a/transport.c b/transport.c
> index 32885f7..5b880d7 100644
> --- a/transport.c
> +++ b/transport.c
> [snip]
This hunk:
> @@ -1055,8 +1056,6 @@ int transport_push(struct transport *transport,
> ret = transport->push_refs(transport, remote_refs, flags);
> err = push_had_errors(remote_refs);
>
> - ret |= err;
> -
> if (!quiet || err)
> print_push_status(transport->url, remote_refs,
> verbose | porcelain, porcelain,
and this hunk:
> @@ -1071,9 +1070,15 @@ int transport_push(struct transport *transport,
> update_tracking_ref(transport->remote, ref, verbose);
> }
>
> - if (!quiet && !ret && !refs_pushed(remote_refs))
> - fprintf(stderr, "Everything up-to-date\n");
> - return ret;
> +
> + if (porcelain) {
> + if (ret==0)
> + fprintf (stdout, "Done\n");
> + } else
> + if (!quiet && !ret && !refs_pushed(remote_refs))
> + fprintf(stderr, "Everything up-to-date\n");
> +
> + return ret | err;
> }
> return 1;
> }
slightly changes the conditions under which "Everything up-to-date" is
printed, since you did away with "ret |= err". I guess you can
mitigate this by adding "!err" to the list of operands:
if (!quiet && !ret && !err && !refs_pushed(remote_refs))
....
Even better, create yet another temporary variable:
push_ret = transport->push_refs(transport, remote_refs, flags);
err = push_had_errors(remote_refs);
ret = push_ret | err;
That way, you can access transport->push_refs() status (what you
want), without messing with the other parts of the code and their
assumptions.
One last thing: could the if statements towards the end be "flattened"?
if (porcelain && ret == 0)
fprintf(stdout, "Done\n");
else if (!quiet && !ret && !refs_pushed(remote_refs))
fprintf(stderr, "Everything up-to-date\n");
(sorry about the lack of tabs, gmail doesn't let me type those easily.)
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-02-27 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 3:59 [PATCH 0/4] ld/push-porcelain Larry D'Anna
[not found] ` <cover.1267243044.git.larry@elder-gods.org>
2010-02-27 3:59 ` [PATCH 1/4] git-push: fix an advice message so it goes to stderr Larry D'Anna
2010-02-27 3:59 ` [PATCH 2/4] git-push: send "To <remoteurl>" messages to the standard output in --porcelain mode Larry D'Anna
2010-02-27 3:59 ` [PATCH 3/4] git-push: make git push --porcelain print "Done" Larry D'Anna
2010-02-27 4:19 ` Tay Ray Chuan [this message]
2010-02-27 3:59 ` [PATCH 4/4] git-push: add tests for git push --porcelain Larry D'Anna
-- strict thread matches above, loose matches on Subject: below --
2010-02-27 4:52 [PATCH 0/4] ld/push-porcelain Larry D'Anna
2010-02-27 4:52 ` [PATCH 3/4] git-push: make git push --porcelain print "Done" Larry D'Anna
2010-02-27 5:22 ` Tay Ray Chuan
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=be6fef0d1002262019j2088d20dp89f1587e3921a1ba@mail.gmail.com \
--to=rctay89@gmail.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.
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).