All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danh Doan <congdanhqx@gmail.com>
To: Christoph Berg <myon@debian.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git clone git clone some://url
Date: Thu, 21 Nov 2019 20:49:28 +0700	[thread overview]
Message-ID: <20191121134928.GA1018@danh.dev> (raw)
In-Reply-To: <20191120064157.GA22081@msg.df7cb.de>

On 2019-11-20 07:41:58+0100, Christoph Berg <myon@debian.org> wrote:
> Re: Junio C Hamano 2019-11-20 <xmqqimnfcikf.fsf@gitster-ct.c.googlers.com>
> > Christoph Berg <myon@debian.org> writes:
> > 
> > > On some git hosting sites [*], if you copy the repository URL, you'll
> > > actually get "git clone some://url" in the cut buffer. When you then
> > > proceed to do "git clone <paste>" in the next terminal window, the
> > > command executed is actually this:
> > >
> > > $ git clone git clone some://url
> > > fatal: Too many arguments.
> > 
> > Or
> > 
> >     $ git git clone some://usr
> >     $ git git git diff
> > 
> > ;-)
> > 
> > I seriously doubt "git" should do anything funky when fed such
> > command lines.
> 
> "git git git" is obviously silly. The problem is really just about
> this single issue:
> 
> 1. go to some website, copy the git url
> 2. type "git clone" in the terminal
> 3. paste the url, hit enter
> 4. be annoyed when you ended up with "git clone git clone url://"

Seriously, people should stop pasting random command from internet
without reading.

Someone had written about paste-hijacking in the past.

c.f. https://news.ycombinator.com/item?id=10554679

-- 
Danh

  reply	other threads:[~2019-11-21 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 14:15 git clone git clone some://url Christoph Berg
2019-11-20  3:50 ` Junio C Hamano
2019-11-20  6:41   ` Christoph Berg
2019-11-21 13:49     ` Danh Doan [this message]
2019-11-20 18:07   ` Denton Liu
2019-11-22  5:44     ` Junio C Hamano
2019-12-04 21:40 ` Jonathan Nieder
2019-12-05 12:35   ` Christoph Berg

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=20191121134928.GA1018@danh.dev \
    --to=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=myon@debian.org \
    /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.