From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Cc: Benjamin Peterson <bp@benjamin-peterson.org>
Subject: [PATCH] vcs_info, hg: Support detecting repos using ShareExtension
Date: Thu, 16 Jan 2014 16:05:11 +0100 [thread overview]
Message-ID: <1389884711-14831-1-git-send-email-ft@bewatermyfriend.org> (raw)
In-Reply-To: <1389883299.24740.71559021.64C873AD@webmail.messagingengine.com>
---
Benjamin Peterson wrote:
> shared repos have a file .hg/sharedpath if that helps
If that's indeed the case, the following should make backend detect such
repositories. I don't know if supporting this requires changes to the _get_data
function as well. Would be good if someone could test this before I push the
patch to the repo...
Regards, Frank
Functions/VCS_Info/Backends/VCS_INFO_detect_hg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Functions/VCS_Info/Backends/VCS_INFO_detect_hg b/Functions/VCS_Info/Backends/VCS_INFO_detect_hg
index a22c1ee..d7b1d0d 100644
--- a/Functions/VCS_Info/Backends/VCS_INFO_detect_hg
+++ b/Functions/VCS_Info/Backends/VCS_INFO_detect_hg
@@ -7,7 +7,7 @@ setopt localoptions NO_shwordsplit
[[ $1 == '--flavours' ]] && { print -l hg-git hg-hgsubversion hg-hgsvn; return 0 }
VCS_INFO_check_com ${vcs_comm[cmd]} || return 1
-vcs_comm[detect_need_file]="store data"
+vcs_comm[detect_need_file]="store data sharedpath"
VCS_INFO_bydir_detect '.hg' || return 1
if [[ -d ${vcs_comm[basedir]}/.hg/svn ]] ; then
--
1.8.4
next prev parent reply other threads:[~2014-01-16 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 1:59 vcs_info for mercurial doesn't detect shared repos Benjamin Peterson
2014-01-16 9:14 ` Frank Terbeck
2014-01-16 14:41 ` Benjamin Peterson
2014-01-16 15:05 ` Frank Terbeck [this message]
2014-01-17 5:48 ` [PATCH] vcs_info, hg: Support detecting repos using ShareExtension Benjamin Peterson
2014-01-17 8:01 ` Frank Terbeck
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=1389884711-14831-1-git-send-email-ft@bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=bp@benjamin-peterson.org \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).