info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

An automatically commit


From: Giohanna MEndez
Subject: An automatically commit
Date: Mon, 18 Nov 2002 14:53:01 -0500

Hi!,

I want to make an automatically commit inside a logical structure I made on my cvs repository,

I use programs in C, and each version has an structure of directories and subdirectories which contain the programs. I have a version base, from it I derive version 1, version 2 and version 3, from version 1 I derive version 11 and version 12, the logical structure is:

                                  /---Version 11
               /---version 1-----/
              /                  \
             /                    \----Version 12
version base /---version 2
            \---version 3 ----- Version 31

Each version has:
version base
   |-----include (inside some files .h)
   |-----server (inside some files .c)
   +-----client (inside some files .c)

version 1
   |-----include (inside same files as include in version base
         and more files .h)
   |-----server (inside same files as server in version base
          and more files .c)
   |-----client (inside same files as client in version base
          and more files .c)
   +-----communications (inside some files .c)

version 2
   |-----include (inside same files as include in version base
          and more files .h -different from version 1)
   |-----server (inside same files as server in version base
          and more files .c -different from version 1)
   +-----client (inside same files as client in version base
          and more files .c -different from version 1)

version 3
   |-----include (inside same files as include in version base
          and more files .h -different from version 1 and version 2)
   |-----server (inside same files as server in version base
          and more files .c -different from version 1 and version 2)
   |-----client (inside same files as client in version base
          and more files .c -different from version 1 and version 2)
   +-----graphics (inside some files .c)

version 31
   |-----include (inside same files as include in version 3
          and more files .h)
   |-----server (inside same files as server in version 3
          and more files .c)
   |-----client (inside same files as client in version 3
          and more files .c)
   +-----graphics (inside same files as graphics in version 3
          and more files .c)

I made this logical structure in this way: first I create the version base, then from the version base I made a checkout, then I modify it and import it with the name version 1, I made the same procedure to create version 2 and 3, It is important to say to each modification is different between each version, to create the version 11, I made a checkout from the version 1, then I modify it and import it with the name version 11, I made the same to create version 12. To obtain version 31: I made a checkout from the version 3, then I modify it and import it with the name version 31.

In this way, I had created modules for each version (at the same level in my cvs repository), but what I want to do is: each time I made a modification in program of the version 1, and I make a commit, the cvs automatically makes a commit for the version 11 and 12. Other example: if I made a commit for a modified program of the version base, cvs make automatically a commit for the dependent versions from it (according to my logical structure). This is my problem: how can I do it automatically?

what I am doing at the moment, that is by the way too expensive, it is:
I make checkout of the version 1, then I modify it, then I made commit, after that and manually I made a checkout of the version 11, then I made the same modification and I made a commit, then I made a checkout of the version 12, then I made the same modification and I made a commit

In the other example,
I made a checkout from the version base, then I modify it, then I made a commit, I made checkout of the version 1, then I made the same modification in it, then I made commit, I made a checkout of the version 11, then I made the same modification and I made a commit, then I made a checkout of the version 12, then I made the same modification and I made a commit, I made checkout of the version 2, then I made the same modification in it, then I made commit, I made checkout of the version 3, then I made the same modification in it, then I made commit, after that, and finally I made checkout of the version 31, then I made the same modification in it, then I made commit,


As I am doing it at the moment, it has its problems because if I forget to make some update, I lose the philosophy of my logical structure and the other problem is that it takes long time to me and much work to do this,

Somebody can help me to make this process more automatically?

Gracias,
        Giohanna

_________________________________________________________________
MSN. Más Útil Cada Día http://www.msn.es/intmap/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]