On Sep 2, 2016, at 16:22, Stefan Sperling wrote:
> If you need a specific set of property changes in your tag, you
> can create a working copy which contains the necessary changes
> and then copy this working copy to a tag.
Yes, I understand this, but...
> We cannot automate details of everybod
On Fri, Sep 02, 2016 at 01:48:03PM -0400, Alfred von Campe wrote:
> On Sep 2, 2016, at 4:07, Bert Huijben wrote:
> >
> > A single argument specifying a revision may only work for very specific
> > scenarios. The --pin-externals feature also works when you have dozens of
> > externals, all point
On Sep 2, 2016, at 4:07, Bert Huijben wrote:
>
> A single argument specifying a revision may only work for very specific
> scenarios. The --pin-externals feature also works when you have dozens of
> externals, all pointing towards different repositories.
Right, but could you consider the follo
Daniel the configuration is very similar to mine and it only partially works.
Did you test your configuration by using "svn log" from the command line? I
did and it still has the same problem.
D:\projects\foo>svn log svn://myrepo/projects/foo
svn: E220001: Item is not readable
Billy Buzzard wrote on Fri, Sep 02, 2016 at 15:28:11 +:
> What do I do if I have a group of trusted developers who are allowed
> to see all projects and another group of non-so-trusted developers who
> are only allowed to see their project?
This:
[groups]
trusted = ...
untrusted
I want to restrict read access to a given respository to specific users, but
when I do and I try to do an "svn log" from the command line I get an error
message saying "E220001: Item not readable". I have read several articles that
say you must give everyone read access ( * = r ) for the svn lo
Hi
Having a reintegration merge issue. Have raised this on stackoverflow
(http://stackoverflow.com/questions/39106047/unable-to-complete-svn-branch-to-trunk-reintegration-missing-revision-on-branch)
Have scanned the manual, and searched online, but not finding my issue:
In preparation for reinte
A single argument specifying a revision may only work for very specific
scenarios. The --pin-externals feature also works when you have dozens of
externals, all pointing towards different repositories.
When adding the feature we determined that we can't handle all these
additional cases using t
