On 2015-04-04 02.19, Reid Woodbury Jr. wrote:
> Thanks for keeping me in the loop!
>
> I have two thoughts on handling input:
>
> As a coder I want to know exactly what's going on in my code. If I've given
> erroneous input I'd like to know about it in the most useful and quickest
> way, never
Thanks for keeping me in the loop!
I have two thoughts on handling input:
As a coder I want to know exactly what's going on in my code. If I've given
erroneous input I'd like to know about it in the most useful and quickest way,
never glossed over, liberally accepted, nor fixed for me even if t
On Apr 2, 2015, at 17:02, Torsten Bögershausen wrote:
On 2015-04-02 21.35, Jeff King wrote:
On Thu, Apr 02, 2015 at 12:31:14PM -0700, Reid Woodbury Jr. wrote:
Ah, understand. Here's my project URL for 'remote "origin"' with a
more meaningful representation of their internal FQDN:
url
On Fri, Apr 03, 2015 at 02:01:55PM -0700, Junio C Hamano wrote:
> Torsten Bögershausen writes:
>
> > This makes my think that it is
> > a) non-standard to have the extra colon
> > b) The error message could be better
>
> For that, perhaps
>
> -ssh: Could not resolve hostname :: nodename no
Torsten Bögershausen writes:
> This makes my think that it is
> a) non-standard to have the extra colon
> b) The error message could be better
For that, perhaps
-ssh: Could not resolve hostname :: nodename nor servname provided, or not
known
+ssh: Could not resolve hostname ":": nodena
On Fri, Apr 03, 2015 at 02:02:15AM +0200, Torsten Bögershausen wrote:
> But not this one:
> ./git fetch-pack --diag-url
> ssh://git.kernel.org:/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
> Diag: url=ssh://git.kernel.org:/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
> Diag: protocol=ssh
> Diag
On 2015-04-02 21.35, Jeff King wrote:
> On Thu, Apr 02, 2015 at 12:31:14PM -0700, Reid Woodbury Jr. wrote:
>
>> Ah, understand. Here's my project URL for 'remote "origin"' with a
>> more meaningful representation of their internal FQDN:
>>
>> url = ssh://rwoodbury@systemname.groupname.online:
2015-04-02 22:06 GMT+02:00 Reid Woodbury Jr. :
> I'm sure I've seen it other places but I can't remember right now.
What you mean is the scp-like syntax: user@host:path/relative/to/home
– but if you write user@host:/path/to/something, it’s relative to /.
You can also achieve paths relative to the h
Yup, removing the colon works in both 2.3.3 and 2.3.4. And I see that the
manual doesn't use the colon! (eg. $ git clone ssh://user@server/project.git).
The usage of the colon looks normal to my eyes because, for instance, SFTP uses
it to set the path on login so this wasn't something I would ha
On Thu, Apr 02, 2015 at 12:31:14PM -0700, Reid Woodbury Jr. wrote:
> Ah, understand. Here's my project URL for 'remote "origin"' with a
> more meaningful representation of their internal FQDN:
>
> url = ssh://rwoodbury@systemname.groupname.online:/opt/git/inventory.git
>
> The "online" is
Ah, understand. Here's my project URL for 'remote "origin"' with a more
meaningful representation of their internal FQDN:
url = ssh://rwoodbury@systemname.groupname.online:/opt/git/inventory.git
The "online" is their literal internal TLD.
Reid
> On Apr 2, 2015, at 12:24 PM, Junio C Ham
Jeff King writes:
> but this does not:
>
> $ git push ssh://does-not-exist:/repo.git
> ssh: Could not resolve hostname does-not-exist:: No address associated with
> hostname
>
> (note the doubled colon). v2.3.3 did strip off that extra colon, but I
> am not sure the URL above (i.e., a colon
On Thu, Apr 02, 2015 at 11:58:13AM -0700, Reid Woodbury Jr. wrote:
> The colons were part of the output. The '' replaces the domain in
> the response.
OK, if the double colons are correct, then that is almost certainly the
problem:
$ ssh does-not-exist
ssh: Could not resolve hostname doe
Peff
The colons were part of the output. The '' replaces the domain in the
response. The domain is an internal one that my client would rather keep
private. But this got me to think that this might be an important detail: I am
using GIT from a remote node on a Cisco AnyConnect VPN with DNS s
On Thu, Apr 02, 2015 at 10:18:33AM -0700, Reid Woodbury Jr. wrote:
> After upgrading from GIT 2.3.3 to 2.3.4 (on Mac OS X 10.10.2,
> installed with MacPorts) I received this error message when doing a
> push:
>
> $ git push
> ssh: Could not resolve hostname :: nodename nor servname provided,
Dear Sirs
After upgrading from GIT 2.3.3 to 2.3.4 (on Mac OS X 10.10.2, installed with
MacPorts) I received this error message when doing a push:
$ git push
ssh: Could not resolve hostname :: nodename nor servname provided, or not
known
fatal: Could not read from remote repository.
It was
16 matches
Mail list logo
