multiple projects per repository and versions

[Vikrama Sanjeeva <vi...@gmail.com>]

Hi all,

Suppose If I have project A and project B in a same repository then project
B's version will change every time project A has something committed to it,
even if no work is being done in project B ?

Please confirm my understanding.

Bye,
Viki.

Re: multiple projects per repository and versions

[Les Mikesell <le...@gmail.com>]

Vikrama Sanjeeva wrote:
> Hi all,
> 
> Suppose If I have project A and project B in a same repository then 
> project B's version will change every time project A has something 
> committed to it, even if no work is being done in project B ?
> 
> Please confirm my understanding.

The global repository revision number increases with every change, even if it 
doesn't affect a project.  However, normally the only revisions you care about 
are the HEAD if you want the latest and known previous revision numbers - and it 
doesn't matter if there are big jumps between them.  Also, for releases or other 
revisions you want to access by your own name/number scheme you can copy to tags 
using whatever conventions you like.

-- 
   Les Mikesell
    lesmikesell@gmail.com

Re: multiple projects per repository and versions

[Vikrama Sanjeeva <vi...@gmail.com>]

On Sat, Apr 3, 2010 at 3:51 AM, Andy Levy <an...@gmail.com> wrote:

> On Fri, Apr 2, 2010 at 20:22, Vikrama Sanjeeva <vi...@gmail.com>
> wrote:
> > Hi all,
> >
> > Suppose If I have project A and project B in a same repository then
> project
> > B's version will change every time project A has something committed to
> it,
> > even if no work is being done in project B ?
>
> Individual items do not have "a version" in Subversion. Think of it in
> reverse - what's the state of the item at revision 123? Every commit
> will increase the global revision number (think of it as a timestamp),
> but the last changed revision of B will remain unchanged until you
> commit a change to B.
>

Agreed. And I understand that if 1 of 100 file is changed and commit then
SVN will revise version of full repository rather than only the changed
file.

  Ok, I got the point. Thank you.

Bye,
Viki.

Re: multiple projects per repository and versions

[Andy Levy <an...@gmail.com>]

On Fri, Apr 2, 2010 at 20:22, Vikrama Sanjeeva <vi...@gmail.com> wrote:
> Hi all,
>
> Suppose If I have project A and project B in a same repository then project
> B's version will change every time project A has something committed to it,
> even if no work is being done in project B ?

Individual items do not have "a version" in Subversion. Think of it in
reverse - what's the state of the item at revision 123? Every commit
will increase the global revision number (think of it as a timestamp),
but the last changed revision of B will remain unchanged until you
commit a change to B.