From: Giovanni Bajo <rasky@develer.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>,
bernie@codewiz.org, git@vger.kernel.org
Subject: Re: [PATCH] Give error when no remote is configured
Date: Tue, 17 Mar 2009 01:12:36 +0100 [thread overview]
Message-ID: <49BEEAF4.40403@develer.com> (raw)
In-Reply-To: <76718490903161301qca2214cta87411bad1b0b8b5@mail.gmail.com>
On 3/16/2009 9:01 PM, Jay Soffian wrote:
> On Mon, Mar 16, 2009 at 12:55 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
>> No default remote is configured for your current branch, and the default
>> remote "origin" is not configured either.
>
> The use of "default" twice is slightly confusing. Perhaps:
>
> No remote is configured for the current branch, and the default
> remote "origin" is not configured either.
I'm a total newbie with git. I must say that the above sentence means
absolutely nothing to me (in either version) because of the confusing
usage of the word "remote" (twice, one as a substantive, one as an
adjective) and the word "origin" which is git jargon which I don't
master yet.
My suggestion is that you should at least add a sentence that points to
a likely solution. Something like:
(use "git remote add" to configure a remote URL)
Note that I don't have any clue if this sentece is correct and/or is the
correct solution. The above is just an example of a helpful error message.
--
Giovanni Bajo
Develer S.r.l.
http://www.develer.com
next prev parent reply other threads:[~2009-03-17 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 5:47 [PATCH] Give error when no remote is configured Daniel Barkalow
2009-03-11 6:19 ` Bernie Innocenti
2009-03-16 7:12 ` Junio C Hamano
2009-03-16 16:55 ` Daniel Barkalow
2009-03-16 20:01 ` Jay Soffian
2009-03-17 0:12 ` Giovanni Bajo [this message]
2009-03-17 16:06 ` Daniel Barkalow
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=49BEEAF4.40403@develer.com \
--to=rasky@develer.com \
--cc=barkalow@iabervon.org \
--cc=bernie@codewiz.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.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 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.