Hi Troy,
Thank you for your prompt answer. Just the information I was looking for.
Our current version control system (commercial software) allow us to create
tasks, then associate a number of files with the task. Developers can then
check out a task. It will check out all files grouped under that task. I
like this feature. I was just trying to find a equivalent in Subversion.
Subversion might want to add such a feature...
Cheers,
Henry
On 3/26/07, Troy Curtis Jr <troycurtisjr@gmail.com> wrote:
>
> On 3/25/07, Henry LS <henrylsun@gmail.com> wrote:
> > Hi all,
> >
> > I am new to subversion. Had some experience with VSS. My first question
> is I
> > tried to just check out few files but seems svn doesn't allow this... It
> > only allow me to check out folder. We have groups of files always need
> to be
> > changed together. They all exist in one folder. I was just wondering if
> I
> > can create something like "task" to logically group a number of files
> > together (instead of creating sub-folders)? Then check in, check out,
> > change and undo change based on those logical groups... The concept
> > ChangeSet looks similar to what I am looking for, but there is not much
> > explanation on how Changeset works... Can anybody shed some light on it?
> > Thank you.
> >
> > HS
>
> Subversion versions directory trees so the smallest unit that can be
> checked out and in is a directory. One reason is that it needs a
> directory to put it's administrative folder (.svn) which is used to
> track all of the Subversion specific meta-data and information for the
> directory and the files/directories it contains.
>
> Every commit to the Subversion repository results in the increase of
> the repository revision number. This commit could contain one, or
> multiple files. In either case it represents a single commit, or
> "Change Set". If you want changes to a set of files to be grouped
> together in a "Change Set", simply make sure that a 'svn ci' operation
> includes them all.
>
> I think that I may see were you were trying to go with that last
> paragraph. You want a logical change set "item" in the repository
> that you can check into and out of. That isn't what a change set in
> Subversion means. You cannot go back and modify some arbitrary change
> set (aka revision), you simply commit new revisions (each revision is
> a change set). So you will have to use subdirectories to accomplish
> what you want.
>
> Troy
> --
> "Beware of spyware. If you can, use the Firefox browser." - USA Today
> Download now at http://getfirefox.com
> Registered Linux User #354814 ( http://counter.li.org/)
>
Received on Mon Mar 26 06:46:21 2007