From: Philip Oakley <philipoakley@iee.email>
To: "L2750558108@outlook.com" <L2750558108@outlook.com>,
git <git@vger.kernel.org>
Subject: Re: Gitk : When the number of commits is small, you can roll up excessively
Date: Sun, 26 Feb 2023 12:26:08 +0000 [thread overview]
Message-ID: <3f11a4d5-6774-ddd9-060e-3e95acb84c69@iee.email> (raw)
In-Reply-To: <BY5PR14MB3560879E6CBDD493C873DB18B1A29@BY5PR14MB3560.namprd14.prod.outlook.com>
A bit of a late response..
On 14/02/2023 06:02, L2750558108@outlook.com wrote:
> Gitk : When the number of commits is small, you can roll up excessively
>
> Reduce :
>
> 1.Create a new respository
> 2.Make 2 Commit
> 3.Go to Gitk to see them
> 4.Scroll up in the commit list and you can see the error
I cannot replicate this problem (on Git-for-Windows git version
2.39.2.windows.1).
What OS, Git and gitk versions are you on?
I created the repo with the commands
phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src (main)
$ git init gitkfault
$ cd gitkfault/
$ echo test>file;git add file;git commit -mfirst
$ echo test2>file;git add file;git commit -msecond
$ gitk &
[1] 1021
I was visualising the commits (lower gitk window) with the "Diff" and
"Patch" settings.
At your step 4, I tried 'scrolling up' both by mouse clicking on the two
commits in the top left window that displays the history, and by using
the left/right arrows displayed just right of the "SHA1 ID" value. No
errors were shown.
(those sha1 arrows are distinct from the 'Find' selection and navigation
capability immediately below the "SHA1 ID" line.
What were the exact errors shown at your step 4?
--
Philip
next prev parent reply other threads:[~2023-02-26 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 6:02 Gitk : When the number of commits is small, you can roll up excessively L2750558108
2023-02-26 12:26 ` Philip Oakley [this message]
[not found] ` <CH2PR14MB35637B8C5593D5F17076E7EEB1AF9@CH2PR14MB3563.namprd14.prod.outlook.com>
2023-02-27 10:00 ` Philip Oakley
2023-02-28 6:35 ` Johannes Sixt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f11a4d5-6774-ddd9-060e-3e95acb84c69@iee.email \
--to=philipoakley@iee.email \
--cc=L2750558108@outlook.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).