From: "Алексей Шумкин" <zapped@mail.ru>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re[2]: [PATCH 3/3] Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variable
Date: Tue, 28 Dec 2010 15:14:09 +0300 [thread overview]
Message-ID: <1393005584.20101228151409@mail.ru> (raw)
In-Reply-To: <4D15E48A.9050805@web.de>
Hi, all.
Well, I rolled back my so-called patch which rose up such a
discussion, and what I did see? Annoying behaviuor is vanished and perfomance of $PS1 is
acceptable (as fast as with the "patch").
I guess, as I said, something changed in Git since I discovered
and solved the problem such a weird way.
So, it seems to me, this patch might be considered unnecessary?
next prev parent reply other threads:[~2010-12-28 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 1:20 [PATCH 1/3] Fixes bug: git-diff: class methods are not detected in hunk headers for Pascal Zapped
2010-12-25 1:20 ` [PATCH 2/3] Fixes bug: git-svn: svn.pathnameencoding is not respected with dcommit/set-tree Zapped
2011-01-04 17:18 ` Thomas Rast
2011-01-04 23:20 ` Eric Wong
2011-02-03 20:28 ` Alexey Shumkin
2011-01-05 11:44 ` Re[2]: " Алексей Шумкин
2010-12-25 1:20 ` [PATCH 3/3] Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variable Zapped
2010-12-25 12:33 ` Jens Lehmann
2010-12-25 13:08 ` Johannes Schindelin
2010-12-26 19:14 ` Junio C Hamano
2010-12-26 22:42 ` Re[2]: " Алексей Шумкин
2010-12-27 11:14 ` Jens Lehmann
2010-12-27 22:06 ` Johannes Schindelin
2010-12-27 22:43 ` Casey Dahlin
2010-12-26 22:25 ` Re[2]: " Алексей Крезов
2010-12-28 12:14 ` Алексей Шумкин [this message]
2011-01-04 17:13 ` [PATCH 1/3] Fixes bug: git-diff: class methods are not detected in hunk headers for Pascal Thomas Rast
2011-01-05 11:53 ` Re[2]: " Алексей Шумкин
2011-01-05 14:23 ` Thomas Rast
2011-01-05 14:31 ` Thomas Rast
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=1393005584.20101228151409@mail.ru \
--to=zapped@mail.ru \
--cc=Jens.Lehmann@web.de \
--cc=Johannes.Schindelin@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.