Kenneth Porter wrote:
> --On Friday, October 13, 2006 1:12 PM -0500 Ted Dennison
> <email@example.com> wrote:
>> Wasn't there recently an argument here for multiple repositories, on the
>> basis that working with revisions can get annoying when the entire
>> repository (and thus every "project" in it) gets a new revision every
>> time something changes?
> "Annoying"? That's hardly a good technical argument. (I realize you're
> quoting a previous thread and that it's not your argument.)
> The revision is not unlike a timestamp. Would one complain that every
> check-in has a unique timestamp?
> In other file-oriented systems, one checks out a previous snapshot of
> a part of the database using a timestamp. In Subversion, one grabs
> that same snapshot by revision number. I find the revision number more
> accurate and reliable.
My 2 cents on revision changing analogies -
If I change a file in a project containing 1000 other files and then
test it on my local working copy before I let anyone else use it and
then I commit those changes, I know that my one file change did not
break the whole program in that one revision. I can always tell the
state of the entire project (repository) at the point in time where I
changed the one file.
In a file-based revisioning system I might change file 1, and Joe Blow
sitting down the hall changes file 487 with some dependencies on file
1. His file looks good to him, and he checks it in. My file looks good
to me, and I check mine in. The project breaks. At that build point,
who do you point the finger at? Was it Joe Blow's changes, or mine? At
what point in time did the project break, and can you role the whole
thing back to a usable,working state easily?
I think the discussion of the revision as a timestamp is a bit vague.
To elaborate on it, the timestamp is used to identify the state of the
repository at virtually any given time. This is where the discussion
goes on a tangent about creating separate repositories for unrelated
My preference and the way I have my repos set up - each project has it's
own repository. If I want to do some sort of work/testing/anything to
one, I don't have to kill the whole development process to do it. From
the developer perspective, they know that their code is segregated by
project. They don't know or care that there are one or many repositories.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Oct 13 23:00:33 2006