I've been using subversion on a directory tree which has quite a lot of
directories that start off with a plus sign and I'm getting error
messages and problems committing changes which I never experienced before.
Are plus signs in directory names handled well by subversion?
Zé
ly.
It's quite possibly that the errors I was stumbling on had absolutely
nothing to do with plus signs in directory names. I'll report back if I
manage to replicate this issue or if I stumble abain on one of those
error messages.
Best regards,
Zé
Is there an official Subversion guide to set a subversion server?
Thanks,
Zé
oid setting up the server yourself, you might consider
looking into a more turnkey solution uch as CollabNet's Subversion Edge
(http://www.collab.net/products/subversion) or WANdisco's uberSVN
(http://www.wandisco.com/ubersvn).
Third-party service providers aren't an option.
Zé
,
--
Zé
On 04/26/2013 12:36 PM, Nico Kadel-Garcia wrote:
Did you mention your base OS? The versions available for different
operating systems vary.
I expect it to be linux, either Debian or Ubuntu.
--
Zé
u are trying to implement the
release branches approach.
--
Zé
t the semantical equivalent of creating a branch. Therefore, if the
same operation is used to perform both then one will not be supported as
well as it could be.
Zé
opular SCM projects understood this right from the start.
Zé
On 05/11/2013 08:46 PM, Stefan Sperling wrote:
On Sat, May 11, 2013 at 06:45:03PM +0100, Zé wrote:
You are misrepresenting the problem. It doesn't matter if subversion
isn't like any other SCM system. The problem is that the effect of
copying, renaming or moving a file or directory
a pointer to a particular point in the repo's history.
--
Zé
Subversion would be better if it supported branching.
--
Zé
ss actually agree
with what has been said about subversion and branches, but that doesn't
mean that referring to the same issue through different names implies
that anyone is dismissing anyone's work.
--
Zé
er directory in your repository. That may be a convenient hack,
but that isn't exactly support for tagging.
Let's put it this way: if that was actually a tag then it could also be
argued that any file system supports branching/tagging.
--
Zé
On 05/15/2013 04:04 PM, Les Mikesell wrote:
On Tue, May 14, 2013 at 3:33 PM, Zé wrote:
What has been said regarding
subversions lack of support for branching was, I think, quite clear.
Well, no. The only thing you've made clear is that you don't like it
or you don't under
the process screw up with the
repo's revision history.
--
Zé
On 05/18/2013 06:33 PM, Thorsten Schöning wrote:
Guten Tag Zé,
am Samstag, 18. Mai 2013 um 18:24 schrieben Sie:
The only difference between subversion and other SCM systems
is that other systems offer support for labeling and adding useful info
to those revisions, while Subversion doesn&#
t make the
project any better than what it already is. What does contribute to its
improvement is providing suggestions on ways to improve it, such as
suggesting that implementing a sorely missed feature would be a
significant improvement. Do you agree?
--
Zé
On 05/18/2013 08:33 PM, David Chapman wrote:
On 5/18/2013 12:01 PM, Zé wrote:
On 05/18/2013 07:16 PM, David Chapman wrote:
You are pretty insistent that there is One True Way to use branches in
development.
No, I'm stating that if all a SCM does is track changes made to the
contents
a development branch subdirectory:
$ svn delete file:///tmp/repository/branches/awesome_feature
7) This is the problem:
$ svn checkout --revision 3 file:///tmp/repository/branches wc
$ cd wc && tree
ze@ubuntu:wc$ tree
.
└── awesome_feature
├── good_idea_but_undoable.c
└── main.c
1 directory, 2 files
--
Zé
On 05/19/2013 09:33 AM, Dave Huang wrote:
I use branches in SVN all the time… you might take
Read the thread.
--
Zé
On 05/19/2013 09:51 AM, Zé wrote:
Again, the problem is that subversion does not support branches or tags.
All it supports is basic file operations on a file system, and they
are not adequate for simulating branches or tags.
Regarding tags, there's a better way to handle them in subve
com/en/1.7/svn.branchmerge.commonpatterns.html#svn.branchmerge.commonpatterns.feature
--
Zé
ich is really important.
http://subversion.apache.org/faq.html#collab
--
Zé
Does subversion support any command line wizardry that offers the user a
way to commit the changes made to all files under version control except
those made to a selected few?
Thanks,
--
Zé
On 09/15/2013 12:31 PM, Andy Levy wrote:
On Sun, Sep 15, 2013 at 6:10 AM, Zé wrote:
Does subversion support any command line wizardry that offers the user a way
to commit the changes made to all files under version control except those
made to a selected few?
If you organize your files into
On 09/15/2013 02:39 PM, Zé wrote:
On 09/15/2013 12:31 PM, Andy Levy wrote:
Other than that, svn commit allows you to pass multiple files/paths to
be committed. You can specify individual paths and/or use your shell
to pattern-match or glob files which should then be expanded by your
shell to
Does subversion provide a way to commit all changes except those that
affect only whitespaces?
Thanks,
Zé
On 09/25/2013 11:37 PM, Ryan Schmidt wrote:
On Sep 25, 2013, at 16:19, Zé wrote:
Does subversion provide a way to commit all changes except those that affect
only whitespaces?
Nothing built in for that, no.
I recommend whitespace changes be a separate commit from functional changes.
But
Does subversion provide a way to fork and merge individual files stored
in various points within a repository? If it does, can anyone provide a
small example showcasing this feature?
Thanks,
Zé
Does subversion provide a way for the user to configure his username,
thus avoiding having to pass the --username flag everytime he has to
commit something?
Thanks
Zé
On 04/18/2014 04:41 PM, Bob Archer wrote:
Does subversion provide a way for the user to configure his username, thus
avoiding having to pass the --username flag everytime he has to commit
something?
Thanks
Zé
The credentials should be cached. If they are not being cached check in
username.
Is there a way to keep these from “sticking"?
sudo to another username when working with the other repository?
It doesn't make much sense to create a new username just to handle a
remote repository. In fact, that's not even possible if the user hasn't
admin privileges.
--
Zé
only need a local svn repository and
don't have the option to set up a server?
Zé
server? Is
it even possible to deploy subversion in that scenario?
Zé
he
top of best practices. Don't you agree?
And I hate to repeat myself, but I'll repeat for the third time this
question: if file:// is not intended to be used, then what are the
available options for those who need a version control system and can't
set up a server?
Zé
On 08/27/2014 05:09 PM, jbl...@icloud.com wrote:
On Aug 27, 2014, at 8:28 AM, Zé wrote:
Additionally, to those security-concious people, installing servers
on your workstation just to access local repositories isn't exactly
on the top of best practices. Don't you agree?
p a server?
Zé
Does the file server support SSH?
There is no file server. This discussion is about local repositories on
a local system (a workstation) managed and accessed by a single user.
Be definition you have a server since the files are on it. Just run
the svnserve deamon on it even if
38 matches
Mail list logo
