From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 8B5F51F47D for ; Sun, 26 Feb 2023 12:26:24 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=iee.email header.i=@iee.email header.a=rsa-sha256 header.s=2023022100 header.b=BaOB2Zc1; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229527AbjBZM0O (ORCPT ); Sun, 26 Feb 2023 07:26:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48914 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229445AbjBZM0N (ORCPT ); Sun, 26 Feb 2023 07:26:13 -0500 Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B60ED1164B for ; Sun, 26 Feb 2023 04:26:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=iee.email; s=2023022100; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID; bh=ZadiCC7k3Sf8vIewy/vEmvuSUOH0cJWwjCzYW8N7geY=; b=BaOB2Z c1pc1uux4WL0zd2th6TU04Egxmzyz10hEnXAimSKTwKjWdmvssN+ZNY1OfhfiLhBOsYuMJmJ00bz9 9TwXRO2Ro1kSjSMOvMO/ZTTC2rFOzHLRZtyRXiVZ2QMuCfoKNSoRYGLZk6J4VpOyi1AzwGfhFelsk JsaGZmIUDQY=; Received: from host-2-103-194-72.as13285.net ([2.103.194.72] helo=[192.168.1.57]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1pWG6T-000BIJ-57; Sun, 26 Feb 2023 12:26:09 +0000 Message-ID: <3f11a4d5-6774-ddd9-060e-3e95acb84c69@iee.email> Date: Sun, 26 Feb 2023 12:26:08 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: Gitk : When the number of commits is small, you can roll up excessively To: "L2750558108@outlook.com" , git References: Content-Language: en-GB From: Philip Oakley In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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