all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>, Eli Zaretskii <eliz@gnu.org>,
	68183@debbugs.gnu.org, Tom Tromey <tom@tromey.com>,
	Juri Linkov <juri@linkov.net>
Subject: bug#68183: 28.3; vc-dir fails when I have a certain branch checked out
Date: Thu, 08 Aug 2024 20:02:00 +0800	[thread overview]
Message-ID: <87sevfmddz.fsf@melete.silentflame.com> (raw)
In-Reply-To: <87zfpnlcg0.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Thu, 08 Aug 2024 09:07:43 +0200")

Hello,

On Thu 08 Aug 2024 at 09:07am +02, Kévin Le Gouguec wrote:

> Do you mean that the detection methods for 'am and 'merge currently in
> place…
>
>     (when (file-exists-p
> 	   (expand-file-name "rebase-apply/applying" gitdir))
>       (push 'am cmds))
>     (when (file-exists-p (expand-file-name "MERGE_HEAD" gitdir))
>       (push 'merge cmds))
>
> … are unreliable somehow?  I wasn't planning on detecting more
> operations, merely adding vc-dir headers for these two, since despite
> vc-git--cmds-in-progress picking these operations up,
> vc-git-dir-extra-headers ignores them 😶

Oh sorry, I misread.  Those tests are reliable.  Yes -- if you think it
would be helpful to have them displayed in vc-dir, it makes sense to me
to add them.

-- 
Sean Whitton





  reply	other threads:[~2024-08-08 12:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 18:59 bug#68183: 28.3; vc-dir fails when I have a certain branch checked out Tom Tromey
2023-12-31 19:34 ` Eli Zaretskii
2023-12-31 20:14   ` Tom Tromey
2024-01-03  9:46     ` Kévin Le Gouguec
2024-02-12  8:08       ` Kévin Le Gouguec
2024-02-14 19:56         ` Kévin Le Gouguec
2024-03-13 20:03           ` Kévin Le Gouguec
2024-03-15  2:57           ` Dmitry Gutov
2024-03-16 17:56             ` Kévin Le Gouguec
2024-03-17  1:06               ` Dmitry Gutov
2024-03-17 18:09                 ` Kévin Le Gouguec
2024-03-18 15:26                   ` Dmitry Gutov
2024-08-07 14:25                     ` Kévin Le Gouguec
2024-08-08  0:32                       ` Sean Whitton
2024-08-08  7:07                         ` Kévin Le Gouguec
2024-08-08 12:02                           ` Sean Whitton [this message]
2024-08-13  1:32                       ` Dmitry Gutov
2024-08-20  6:15                         ` Kévin Le Gouguec
2024-08-20 12:15                           ` Eli Zaretskii
2024-08-22  7:15                             ` Kévin Le Gouguec
2024-08-22 12:46                               ` Eli Zaretskii
2024-08-29 15:36                                 ` Kévin Le Gouguec
2024-08-29 15:46                                   ` Eli Zaretskii
2024-08-29 16:41                                     ` Kévin Le Gouguec
2024-08-21  0:42                           ` Dmitry Gutov
2024-08-21  1:40                             ` Sean Whitton
2024-08-21  7:05                               ` Kévin Le Gouguec
2024-08-21  7:59                                 ` Sean Whitton
2024-08-21 12:29                                   ` Dmitry Gutov

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=87sevfmddz.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=68183@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=kevin.legouguec@gmail.com \
    --cc=tom@tromey.com \
    /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.