Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Issue with vcs_info and zsh 4.3.14
- X-seq: zsh-workers 29954
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Pierre Schmitz <pierre@xxxxxxxxxxxx>
- Subject: Re: Issue with vcs_info and zsh 4.3.14
- Date: Wed, 7 Dec 2011 22:24:01 +0200
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=mesmtp; bh= m6OdsONkL3Ecmrik8VyLB/5Hhpg=; b=pYL950v0y/h2m7BMjQfMUJAEAYfQzenY USmw7EjtRZCPatPHZ7kT0qx7oS7DLQFJ98rs87oA/C+Ixlt1oHEVoXnAHfM986wi PKtLLP2y2DuLUVZoRJVVSzWb6b4qcRUL4sjxlyU/es9+13ptjwk/jipQn3vleK2i w7x8hM//JiI=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=m6OdsONkL3Ecmrik8VyLB/5Hhpg=; b=ReCLUwfU1vLaU0Zo2k9f/3/WtX3n wH6njUfeHEN7EfXdiqnxpO3gTmb+VLFxbli3wflyrUQHNZannOh0e3nLzVc5bEK/ /D4i3iiC2dEBzxzvhGrw+rzrPKBRYLGeasxPbaS/8CYTpLgIF2CM2WQfDvzbs7xo kcdJSDiP5cijK4U=
- In-reply-to: <91f8bdbd8b04c960f177e97d58423a08@archlinux.de>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <91f8bdbd8b04c960f177e97d58423a08@archlinux.de>
Pierre Schmitz wrote on Wed, Dec 07, 2011 at 15:03:47 +0100:
> Hi all,
>
> after upgrading from 4.3.12 to 4.3.14 I noticed that my vcs_info always
> prints a warning if the current dir is not tracked by svn (but a parent
> dir is). This breaks the grml-zsh-config for example.
>
> How to reproduce:
> $ svnadmin create /tmp/foo
> $ svn co file:///foo bar
> $ mkdir bar/blah
> $ cd bar/blah
> $ vcs_info
> svn: '.' is not a working copy
>
Unversioned subdirectory of a working copy?
From a libsvn_wc perspective, the things to beware of here are tree
changes (uncommitted add/rm of directories; these may nest) and
non-direct-child externals --- namely, svn:externals properties on
directory X that create X\foo\bar\baz.
In practice, though, taking care of non-nested dir add/rm's should
address the vast majority of use-cases.
> I also noticed that when calling VCS_INFO_get_data_svn svn complains
> about the unknown option --non-interactive.
>
All svn subcommands accept --non-interactives.
> Let me know if you need more info.
>
> Greetings,
>
> Pierre
>
> --
> Pierre Schmitz, http://pierre-schmitz.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author