From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2012, #01; Tue, 3)
Date: Wed, 4 Jul 2012 03:28:13 -0400 [thread overview]
Message-ID: <20120704072813.GD24807@sigill.intra.peff.net> (raw)
In-Reply-To: <7vd34ctoub.fsf@alter.siamese.dyndns.org>
On Tue, Jul 03, 2012 at 04:19:24PM -0700, Junio C Hamano wrote:
> [Discarded]
> [...]
>
> * jk/no-op-push-message (2012-05-30) 1 commit
> . improve no-op push output
>
> Rewords the status message of "git push" that pushed only one ref
> differently from "Everything up-to-date", to give a bit more help to
> people who get the message when their current branch is not pushed.
>
> I had an impression after the discussion thread that a redesign is
> coming, but it hasn't happened yet.
After our discussion, I was not really convinced that it was a good
direction to go in. So I'm happy to scrap this for now, and somebody may
or may not come up with something better later.
-Peff
next prev parent reply other threads:[~2012-07-04 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 23:19 What's cooking in git.git (Jul 2012, #01; Tue, 3) Junio C Hamano
2012-07-04 7:28 ` Jeff King [this message]
2012-07-10 17:29 ` Ramsay Jones
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=20120704072813.GD24807@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).