From: Bruno Moreira-Guedes <brunodout.dev@gmail.com>
To: Raphael Biersbach <raphael.biersbach@gmx.net>, git@vger.kernel.org
Subject: Re: Bug - added changes are not shown in the diff view anymore ( not added
Date: Mon, 18 Oct 2021 23:47:12 -0300 [thread overview]
Message-ID: <d7de2654254a8b542deda4b11475bc919b87c3f9.camel@gmail.com> (raw)
In-Reply-To: <7d2751d1-949e-cc90-4063-f9f576c6febf@gmx.net>
On Mon, 2021-10-18 at 16:40 +0200, Raphael Biersbach wrote:
>
> Greetings,
>
> when using gitk I am encountering this bug:
>
> - added changes are not shown in the diff view anymore ( not added
> changes and commits are fine)
I tried to reproduce through with the version on "master" branch
with the following steps:
1. I have written a new file with some short text
2. I added it to index with `git add`
3. I ran gitk
4. I went to the top point in the graph, "Local changes checked
in to index but not commited"
5. I verified Diff option was checked
I got precisely what I would expect:
Author:
Committer:
Parent: 9b803221a51430fc491a4b3536bb8a1088c1af6e (Update
README.md)
Branch:
Follows:
Precedes:
Local changes checked in to index but not committed
----------------------- test.txt -----------------------
new file mode 100644
index 0000000..9daeafb
@@ -0,0 +1 @@
+test
If I did something different from what you have in mind,
could you please add the steps you can do to reproduce the
problem? Also, could you check if the reported behavior
appears on git's latest version (from "master" branch)?
>
> git version 2.33.0
>
> running on 5.10.70-1-MANJARO , window manager i3
>
>
> Raphael Biersbach
prev parent reply other threads:[~2021-10-19 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 14:40 Bug - added changes are not shown in the diff view anymore ( not added Raphael Biersbach
2021-10-19 2:47 ` Bruno Moreira-Guedes [this message]
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=d7de2654254a8b542deda4b11475bc919b87c3f9.camel@gmail.com \
--to=brunodout.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=raphael.biersbach@gmx.net \
/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).