From: Junio C Hamano <gitster@pobox.com>
To: Christopher Tiwald <christiwald@gmail.com>
Cc: Clemens Buchacher <drizzd@aon.at>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH] push: Provide situational hints for non-fast-forward errors
Date: Fri, 16 Mar 2012 15:00:57 -0700 [thread overview]
Message-ID: <7vty1odx46.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vk42kh11k.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 16 Mar 2012 11:07:51 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> After reading the fix-up patch again, I actually have a couple of
> comments/reservations myself.
>
> (1) I suggested (and the fix-up patch does so) to use a single existing
> advice configuration, but ...
>
> (2) The advice to "Your current branch is OK but you are also pushing
Well, (2) is untrue. Between message-advice-checkout-pull-push and
message-advice-use-upstream, we already capture this difference just fine.
Sorry about the noise.
next prev parent reply other threads:[~2012-03-16 22:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 23:22 [PATCH] push: Provide situational hints for non-fast-forward errors Christopher Tiwald
2012-03-14 4:27 ` Junio C Hamano
2012-03-14 12:14 ` Zbigniew Jędrzejewski-Szmek
2012-03-14 13:00 ` Matthieu Moy
2012-03-14 14:27 ` Zbigniew Jędrzejewski-Szmek
2012-03-14 16:40 ` Christopher Tiwald
2012-03-15 8:54 ` Clemens Buchacher
2012-03-15 18:06 ` Junio C Hamano
2012-03-16 8:19 ` Matthieu Moy
2012-03-14 14:48 ` Christopher Tiwald
2012-03-14 14:53 ` Christopher Tiwald
2012-03-14 9:06 ` Matthieu Moy
2012-03-14 15:52 ` Christopher Tiwald
2012-03-14 17:26 ` Junio C Hamano
2012-03-16 5:36 ` Junio C Hamano
2012-03-16 9:10 ` Clemens Buchacher
2012-03-16 12:03 ` Junio C Hamano
2012-03-16 17:20 ` Christopher Tiwald
2012-03-16 18:07 ` Junio C Hamano
2012-03-16 22:00 ` Junio C Hamano [this message]
2012-03-16 21:41 ` Clemens Buchacher
2012-03-16 21:53 ` Junio C Hamano
2012-03-16 22:01 ` Clemens Buchacher
2012-03-16 22:10 ` Junio C Hamano
2012-03-17 17:10 ` [fixup PATCH] " Zbigniew Jędrzejewski-Szmek
2012-03-17 18:46 ` Christopher Tiwald
2012-03-17 19:42 ` Zbigniew Jędrzejewski-Szmek
2012-03-19 0:15 ` Junio C Hamano
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=7vty1odx46.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christiwald@gmail.com \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.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).