zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: Re: PATCH: Update VCS_INFO_detect_svn for Subversion 1.7
Date: Wed, 09 Nov 2011 13:49:47 +0100	[thread overview]
Message-ID: <87boslzcic.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <86sjlxoows.knu@iDaemons.org> (Akinori MUSHA's message of "Wed, 09 Nov 2011 14:17:23 +0900")

Akinori MUSHA wrote:
> The attached patch fixes vcs_info not working under a subversion 1.7
> working directory.
[...]
> -{ [[ -f ".svn/entries" ]] || [[ -f ".svn/format" ]] } && return 0
> -return 1
> +vcs_comm[detect_need_file]="entries format"
> +VCS_INFO_bydir_detect '.svn' || return 1

Oh yes, Subversion 1.7. If I understood things correctly, they put their
`.svn' sub-directory only into the root directory of the sandbox.

While the patch fixes detection for both 1.7 and before, we'll do the
same again (the directory traversal) in VCS_INFO_get_data_svn where the
system tries to find out, what the root directory of the sandbox is.
With 1.7 that won't be required, with 1.6 and before it is. So that
would be unnecessary work for 1.7.

I was kind of hoping to do this with a clever detection algorithm, which
would work for both versions and still reveal the sandbox's root
directory. So that we could scratch the root-retrieval from the
`_get_data_' function altogether.

The other way would be to look at "svn --version -q" and check if the
`_get_data_' function still needs to find the root directory. But I'd
actually like to avoid the additional `fork()'. (If you every tried
vcs_info on cygwin, you'll know what I mean.)

Ideas?

Regards, Frank


  reply	other threads:[~2011-11-09 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  5:17 Akinori MUSHA
2011-11-09 12:49 ` Frank Terbeck [this message]
2011-11-09 13:58   ` Frank Terbeck
2011-11-09 15:57     ` Bart Schaefer
2011-11-09 16:07       ` Daniel Shahaf
2011-11-09 16:12       ` Jérémie Roquet
2011-11-09 16:30 ` 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=87boslzcic.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.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).