I think the best will be one project = one repository.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Versions group.
To post to this group, send email to versions@googlegroups.com
To unsubscribe from this group,
As you have things already organized by client, I would say that it
would be better to go for the repository per client.
This would be dependant on how much versioning/rollbacks/merges
required is required.
So in effect you would have a subfolder for each project you have done
for a client
I'd vote for the same, (one repository per client, not per project)
especially if you have a hosted SVN account — you may run out of free
repositories, depending on your host. Adding a directory to a
repository is easier than setting up a new repository each time a new
project comes along,
I'm setting up my development environment for a project with a new
client and need to reach a repository which is behind a proxy
server...
My Windoze-based colleagues are taking great pleasure in telling me
how easily TortoiseSVN handles this, whilst I have been having a
little Google around and
Hi Arnold,
I just resent your license, if you don't see it in your inbox, please
check any junk mail folders you may have.
If you ever lose it again, you can always enter your email address in
the Lost your license? box at the bottom of www.versionsapp.com/support
to get it again.
All the
Thanks everyone! I hadn't thought about the one client per repository
notion, but that makes a lot of sense.
Thanks again!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Versions group.
To post to this group, send
Specifically Trac.
I have not attempted this yet, but is there a way in which commits
could be linked to a bug number?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Versions group.
To post to this group, send email
