Re: Re: log across copies?

> I should also point out that your use-case of 'wanting to see every
> change ever made to a file, on every branch of the file' is a very
> file-centric way of thinking. Subversion development tends to work
> differently.
>
> Rather than branching individual files, the convention is to branch
> whole trees -- whole copies of a project. Atomic commits are thought of
> as "changesets", and changesets are applied to entire project branches,
> and are ported between project branches.
>
> So the usual question isn't, "who changed this file in any branch?", but
> rather "what changes happened on this whole-project branch? and which
> changes were ported to this other whole-project branch?"

That's find if branches are just used for projects, but we use branches to contain developer changes. This is preferred so commits can be made, others can view the branches, and backups occur.

File centric is the reality isn't it? When I have to go to a repository for purposes of finding an introduced regression, it's usually a file.

Maybe I'm the odd case, I thought it was a pretty common to walk down revisions to find the diff that broke it.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 29 22:12:05 2004