From: "Clébio C. Felix" <clebiofelix@yahoo.com.br>
To: Konstantin Khomoutov <kostix+git@007spb.ru>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [BUG] GITK don't show unstaged changes
Date: Fri, 16 Jun 2017 11:27:39 +0000 (UTC) [thread overview]
Message-ID: <1466340834.14042132.1497612459300@mail.yahoo.com> (raw)
In-Reply-To: <20170616063031.mxx72dlg5ccc3vtq@tigra>
If this is an intentional change and not a bug, then gitk has become less useful to me, since I've always used it to do a quick review before committing. It's easier than using bash. Sad.
:-(
________________________________
De: Konstantin Khomoutov <kostix+git@007spb.ru>
Para: Clébio C. Felix <clebiofelix@yahoo.com.br>
Cc: git@vger.kernel.org
Enviadas: Sexta-feira, 16 de Junho de 2017 3:30
Assunto: Re: [BUG] GITK don't show unstaged changes
On Thu, Jun 15, 2017 at 11:52:46AM +0000, Clébio C. Felix wrote:
> Details: https://github.com/git-for-windows/git/issues/1203
>
> Version with bug: 2.13.1
> Normal: 2.13.0
Attached are the pictures for those who doesn't want to browse that bug
and dig them up.
Basically, the idea is that Gitk in 2.13.1 won't show that "Local
uncommitted changes blah blah ..." entry above the one representing the
tip commit even though the `git status` command shows them.
next prev parent reply other threads:[~2017-06-16 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <905919609.12947564.1497527369339.ref@mail.yahoo.com>
[not found] ` <905919609.12947564.1497527369339@mail.yahoo.com>
2017-06-15 11:52 ` [BUG] GITK don't show unstaged changes Clébio C. Felix
[not found] ` <20170616063031.mxx72dlg5ccc3vtq@tigra>
2017-06-16 11:27 ` Clébio C. Felix [this message]
2017-06-16 12:09 ` Konstantin Khomoutov
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=1466340834.14042132.1497612459300@mail.yahoo.com \
--to=clebiofelix@yahoo.com.br \
--cc=git@vger.kernel.org \
--cc=kostix+git@007spb.ru \
/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).