From: Crls <kaploceh@gmail.com>
To: git@vger.kernel.org
Subject: ctrl-z ignored by git; creates blobs from non-existent repos
Date: Fri, 13 Jan 2023 17:01:01 -0500 [thread overview]
Message-ID: <632d051b-d81b-b35d-0641-c2488a124810@gmail.com> (raw)
Ctrl-Z is ignored by git; Git-clone injects blobs even with non-existent
repos
Steps to reproduce 1- git clone github
whateverrepo/whatevernonexistentrepo or 1- git clone gitlab
whateverrepo/whatevernonexistentrepo 2= Git prompts for a username
3- Press Ctrl-Z to stop *git* from running either on the virtual
console/tty *git* automatically creates blobs with directories and
disregards
^Z altogether It goes ahead anyway and creates pleases. It looks as if
^Z is not enough.
Expected: The same issue does not happen with other non-existent repos
e.g., git clone git.zx2c4/ it returns the message of fatal repo not found
According to console_codes (4) CAN (0x18, ^X) and SUB (0x1A, ^Z)
abort escape sequences should be clear enough
git version 2.36.3
next reply other threads:[~2023-01-13 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 22:01 Crls [this message]
2023-01-15 15:45 ` ctrl-z ignored by git; creates blobs from non-existent repos Theodore Ts'o
2023-01-15 18:36 ` Jeff King
2023-01-15 22:47 ` Crls
2023-01-15 23:33 ` Jeff King
2023-01-17 22:40 ` Crls
2023-01-16 2:07 ` 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=632d051b-d81b-b35d-0641-c2488a124810@gmail.com \
--to=kaploceh@gmail.com \
--cc=git@vger.kernel.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 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).