Steve Bakke <steven.bakke <at> amd.com> writes:
> For c) I assume that you mean you'd like to see *both the checkin timestamp
> in addition to the last-modified timestamp. If so, I definitely agree.
> I will also add mine to the list:
> 1) There have been numerous discussions on this list regarding svn-style
> "tags" and cvs-style tags.
At least more documentation about tags would be a good idea, and less
patronising comments when people popup to ask 'how do I do labels?' :)
I think, as a tag is really just a branch, SVN might as well not bother with
tags at all. Also, I really feel the documented 'best practise' regarding
tags, branches and trunk subdirectories is wrong. I (and several others, from
reading these lists) think a top-level directory is a much better best
practise repository organisation and should be encouraged. (such an
organisation allows multiple projects to be branched as one, and stops
project directories being cluttered with the meta-folders.)
> 4) The way that subversion client config is handle is annoying. I'm in an
> environment, where the "default" configuration doesn't apply to everyone on
> the machine.
At least allow the ability to specify client configuration at the server.
I'm sure it could be cached on the client so network traffic wouldn't be
much of a problem along with a 'dirty' flag style update mechanism if it
was ever changed (or even bouncing of the server process to refresh the
client would be acceptable).
I'd love to prevent build objects from being checked into the repository,
but every so often someone ends up installing svn client, forgets to
update the ignore list, adds a new project... and suddenly a project
is filled with temporary files.
A follow-up to this global config request is for a way to delete
accidentally-added files from a repository, or to remove revisions (eg, I
store executable objects, so the installation guys can get the latest
without having to re-build a project. After a couple of releases, the
old binaries could be deleted to free up a considerable amount of space).
One more thing that I'd like to manage is the ability to checkout on top of
an existing working folder that does not have the .svn folder. Ie, when I
add a project, I would like SVN to create the necessary details so it
appears as a SVN working copy without having to delete and checkout.
Similarly, I will occasionally get a zip of a folder that is stored in
SVN. I'd like to be able to tell SVN that the local copy is actually
stored in SVN at a particular location and have it tell me which files
are changed without me having to checkout, and then overwrite the
local files. A 'relocate location' style command that doesn't need
an existing .svn folder would be great.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jan 31 20:00:33 2007