From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 0/3] more terse push output
Date: Mon, 05 Nov 2007 13:14:43 -0800 [thread overview]
Message-ID: <7v7ikwpf7g.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20071105050517.GA6244@sigill.intra.peff.net
Jeff King <peff@peff.net> writes:
> - the 'ref is not up-to-date, maybe you need to push' message has gone
> away in favor of the terse '[rejected] ... (non-fast forward)'. I
> know there was some discussion recently of enhancing that message.
> Is this perhaps too terse?
I kind of like this part.
I also like the part that stops mentioning the "pretend fetching
back" action. This would mostly parrot the same set of refs for
people who do use the tracking branches anyway.
prev parent reply other threads:[~2007-11-05 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 5:05 [PATCH 0/3] more terse push output Jeff King
2007-11-05 5:11 ` [PATCH 1/3] " Jeff King
2007-11-05 5:11 ` [PATCH 2/3] receive-pack: don't mention successful updates Jeff King
2007-11-05 5:12 ` [PATCH 3/3] send-pack: require --verbose to show update of tracking refs Jeff King
2007-11-05 7:09 ` [PATCH 0/3] more terse push output Steffen Prohaska
2007-11-05 21:14 ` Junio C Hamano [this message]
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=7v7ikwpf7g.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=peff@peff.net \
/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).