From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19343-done@debbugs.gnu.org
Subject: bug#19343: 25.0.50; [vc-git] Unregistered file becomes `up-to-date' in vc-dir buffer after editing and saving
Date: Mon, 1 May 2017 04:36:13 +0300 [thread overview]
Message-ID: <b2f98f01-6050-e957-657e-44d0aed0f1bd@yandex.ru> (raw)
In-Reply-To: <834msuwagv.fsf@gnu.org>
On 17.12.2014 17:40, Eli Zaretskii wrote:
>>> What's our minimum version?
>>
>> Debian Stable has 1.7.10.4, but CentOS 6 - only 1.7.1.
>>
>> So apparently we can use `status --short' (or rather --porcelain), but
>> --ignored is no-go for now.
>
> Why can't we use --ignored when it's available? It doesn't feel right
> to me to punish users of newer versions just because someone else out
> there might not have such a version.
I've just pushed a patch (24301c8148f5f3220d7e597c73a59551cfa10eea)
which fixes this bug, and also uses ---ignored, because that's how the
Jonathan wrote it.
Do we still care about CentOS 6? The previous message in this discussion
has been more than 2 years ago.
If so, we can remove --ignored from the call in vc-git-state, it's not
hugely important there. It will be more important when we decide to
reimplement vc-git-status-files in the same fashion, though.
next prev parent reply other threads:[~2017-05-01 1:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 22:15 bug#19343: 25.0.50; [vc-git] Unregistered file becomes `up-to-date' in vc-dir buffer after editing and saving Dmitry Gutov
2014-12-15 12:01 ` Dmitry Gutov
2014-12-17 4:28 ` Dmitry Gutov
2014-12-17 13:19 ` Dmitry Gutov
2014-12-17 15:40 ` Eli Zaretskii
2014-12-17 17:11 ` Dmitry Gutov
2014-12-17 18:15 ` Eli Zaretskii
2017-05-01 1:36 ` Dmitry Gutov [this message]
2017-05-01 7:10 ` Eli Zaretskii
2017-05-01 15:00 ` Dmitry Gutov
2017-05-01 15:14 ` Eli Zaretskii
2017-05-01 16:55 ` Dmitry Gutov
2017-05-01 19:09 ` Eli Zaretskii
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=b2f98f01-6050-e957-657e-44d0aed0f1bd@yandex.ru \
--to=dgutov@yandex.ru \
--cc=19343-done@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.