Jabdah does this a lot (the last planet bass too), you guys need to remeber, once you make it through ATE, you cannot change the ID3, the nfo, or anything. If you do, you will need remake the sfv by hand, or retag it. ------------------- > -------------------------- eGroups Sponsor -------------------------~-~> > Get a NextCard Visa with rates as low as 2.99% Intro APR! > 1. Fill in the brief application > 2. Get approval decisions in 30 seconds! > http://click.egroups.com/1/9336/4/_/1533/_/970383711/ > ---------------------------------------------------------------------_ -> > > There are 3 messages in this issue. > > Topics in this digest: > > 1. An Online Fair of China's Electronic Products > From: "[EMAIL PROTECTED]"<[EMAIL PROTECTED]> > 2. Isolating baseline from checkins > From: Matthew Berney <[EMAIL PROTECTED]> > 3. make errors 1.10-8 > From: "Kurt V. Hindenburg" <[EMAIL PROTECTED]> > > > ______________________________________________________________________ __ > ______________________________________________________________________ __ > > Message: 1 > Date: Sun, 01 Oct 2000 00:37:46 > From: "[EMAIL PROTECTED]"<[EMAIL PROTECTED]> > Subject: An Online Fair of China's Electronic Products > > > > [This message is not in displayable format] > > > > ______________________________________________________________________ __ > ______________________________________________________________________ __ > > Message: 2 > Date: Sat, 30 Sep 2000 12:01:51 -0700 > From: Matthew Berney <[EMAIL PROTECTED]> > Subject: Isolating baseline from checkins > > In our current environment, we have a problem maintaining a stable baseline. > The problem is that everyone checks into the tip and then we build from the > tip. Then we have to sort everything out afterwards. > > A few approaches have been considered (personal branches, and static tags). > Branches would work, but they are complicated to keep up-to-date. Static > tags on the other hand, are simpler, but how do you handle two people > tagging different revisions of the same file? > > Looking at this problem from a build point of view: > 1) Apply a static tag to the entire repository (this is our baseline) > 2) Developers tag the individual files that they work on > 3) Update to the baseline + developer's tag. > > Are there any scripts out there to help a developer keep track of the files > being worked on. For example, looking at this problem from the developer's > point of view: > 1) Update to the baseline > 2) Update "my files" to the tip > 3) When ready to "integrate" changes to the baseline, tag "my files". > > How do people use CVS in a large organization? How do you isolate the > baseline from developers checkins? > > Thanks in advance, > > Matt > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > > > ______________________________________________________________________ __ > ______________________________________________________________________ __ > > Message: 3 > Date: Sun, 1 Oct 2000 00:43:01 -0500 > From: "Kurt V. Hindenburg" <[EMAIL PROTECTED]> > Subject: make errors 1.10-8 > > When compiling cvs 1.10-8 with: > ./configure --disable-server; make > no problems > > ./configure --disable-client; make > log.o: In function `send_one': > log.o(.text+0x1a): undefined reference to `send_to_server' > log.o(.text+0x25): undefined reference to `send_to_server' > log.o(.text+0x49): undefined reference to `send_to_server' > log.o(.text+0x5b): undefined reference to `send_to_server' > collect2: ld returned 1 exit status > > ./configure --disable-client --disable-server; make > create_adm.c: In function `Create_Admin': > create_adm.c:42: `CLIENT_SERVER_STR' undeclared (first use in this function) > create_adm.c:42: (Each undeclared identifier is reported only once > create_adm.c:42: for each function it appears in.) > make[1]: *** [create_adm.o] Error 1 > > Running Linux 2.4.0-test? glibc2.1 gcc-2.95.2 > > Kurt > > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > > > ______________________________________________________________________ __ > ______________________________________________________________________ __ > > > > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
