git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rohit Ner <rohitner1@gmail.com>
To: git@vger.kernel.org
Subject: git log causing hang while browsing upstream linux
Date: Wed, 5 Apr 2023 01:43:09 +0530	[thread overview]
Message-ID: <CAKazavxTXwcZFtL2XyU3MpaUR=snWY8w8Lwpco+mkbqm2nWE=w@mail.gmail.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
1. git clone https://github.com/torvalds/linux.git
2. git checkout master
3. git log --oneline --graph

What did you expect to happen? (Expected behavior)
See a graph of onelined commit histories

What happened instead? (Actual behavior)
Hang after entering the command

What's different between what you expected and what actually happened?
The output is empty and the cursor is stuck. Cursor is unresponsive to any key
press other than ^C which leads to an output like below
### OUTPUT START ###
...
~
~
~
~
(END)
### OUTPUT END ###
Pressing q key helps get the prompt back.

Anything else you want to add:

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
compiler info: gnuc: 12.2
libc info: glibc: 2.36
$SHELL (typically, interactive shell): /bin/bash


[Enabled Hooks]
commit-msg
pre-commit
prepare-commit-msg

             reply	other threads:[~2023-04-04 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 20:13 Rohit Ner [this message]
2023-04-04 20:27 ` git log causing hang while browsing upstream linux Kristoffer Haugsbakk
2023-04-04 20:50   ` Kristoffer Haugsbakk
2023-04-10 17:07     ` Rohit Ner
2023-04-11  0:00       ` Taylor Blau
2023-04-11  9:45         ` Kristoffer Haugsbakk
2023-04-16  7:09         ` SZEDER Gábor
2023-04-16 12:46           ` How to write to the commit graph on clone? Kristoffer Haugsbakk
2023-04-16 15:24             ` Ævar Arnfjörð Bjarmason

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='CAKazavxTXwcZFtL2XyU3MpaUR=snWY8w8Lwpco+mkbqm2nWE=w@mail.gmail.com' \
    --to=rohitner1@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).