From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add suggestion to hard-to-understand error message
Date: Thu, 22 Dec 2005 11:03:23 +0100 [thread overview]
Message-ID: <43AA79EB.6040800@op5.se> (raw)
In-Reply-To: <7vd5jqvsn1.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> In a sense, both are "pull first?" situation, and it probably is
> more confusing to give different messages to the user in these
> two cases. From the end-user point of view they are the same
> "remote is not strict subset.".
>
In non-git'ish, does this mean "you're not up to date, so pull before
pushing" ? If so, why not say so? I'm sure it could prevent a fair few
problems for users (not least those new to scm's).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-12-22 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 23:49 [PATCH] Add suggestion to hard-to-understand error message Johannes Schindelin
2005-12-22 1:15 ` Junio C Hamano
2005-12-22 10:03 ` Andreas Ericsson [this message]
2005-12-22 19:27 ` Junio C Hamano
2005-12-22 20:41 ` [PATCH] send-pack: reword non-fast-forward " Junio C Hamano
2005-12-22 20:53 ` Johannes Schindelin
2005-12-23 12:13 ` Andreas Ericsson
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=43AA79EB.6040800@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.