I had just done and update so I thought I was safe. Live and learn. I think I backed out those changes (whatever they were) but I am not totally sure.
On 8/16/05, Jeff Squyres <[EMAIL PROTECTED]> wrote: > I yell at my students when they do this; you should ALWAYS run "svn > status" before you commit to ensure that you only commit what you > really intend to commit. ;-) > > You should back out this commit if there's a bunch of stuff in here > that you didn't intend to commit, or otherwise should not have been > committed. > > You can always specify a list of files and/or directories that you want > to commit. For example: > > cd svn/oscar <-- my top-level OSCAR checkout directory > cd doc > svn ci > > This would have committed just in the "doc" directory and below. > Alternatively, you could have done: > > cd svn/oscar > svn ci doc > > Which would have done the same thing. > > "svn help" gives a full overview of all the command line options; "svn > help foo" gives help for the svn command "foo". > > > > On Aug 16, 2005, at 4:36 PM, Michael Edwards wrote: > > > Did this checkin for the release-notes.tex and ended up checking in > > some junk that I assume is from ./autogen.sh or somesuch. What is the > > right way to do this so I don't litter up the trunk. I figure I > > should get this right before I put anything in the 4.2 branch. > > > > Not used to commandline svn, TortiseSVN would confirm the file list > > before committing. > > > > *** > > [EMAIL PROTECTED] oscar]$ svn ci -m "4.2 Release notes update. > > Items rearanged for readability, old items removed. Added release > > notes for FC3, RHEL4, and a placeholder for Mandrivia 10" > > Sending doc/installation/release-notes.tex > > Sending lib/OSCAR/PackageBest.pm > > Sending lib/OSCAR/PackageInUn.pm > > Sending lib/OSCAR/SISBuildSetup.pm > > Sending lib/OSCAR/Tk.pm > > Sending packages/mta-config/scripts/post_server_rpm_install > > Sending scripts/opd > > Sending scripts/oscar_home.csh.in > > Sending scripts/oscar_home.sh.in > > Sending scripts/wizard_prep > > Transmitting file data .......... > > Committed revision 3516. > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > > Practices > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > > & QA > > Security * Process Improvement & Measurement * > > http://www.sqe.com/bsce5sf > > _______________________________________________ > > Oscar-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/oscar-devel > > > > -- > {+} Jeff Squyres > {+} [EMAIL PROTECTED] > {+} http://www.lam-mpi.org/ > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Oscar-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-devel > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
