The main reason I don't just do commits from the command line or KDE or whatever (which I did do for a while last week), is that I'm trying to get the bug fixed, and gather data about it. If I aggregate the commits, it means more changes come through with no details. I'd prefer to have only a single file change go through without details, rather than say the whole of the Struts plugin for example.
I've found a good way now as well to make NetBeans easily show me all the files changed by me in the workspace without running an update or committing stuff I don't want to. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers James Taylor <jtaylor@4lane To: Turbine Maven Developers List .com> <[EMAIL PROTECTED]> cc: 05/22/02 10:00 Subject: Re: cvs commit: jakarta-turbine-maven/xdocs/ref/struts PM properties.xml navigation.xml index.xml futures.xml dirlayout.xml Please respond build-file.xml to "Turbine Maven Developers List" > I would if the &^%&^$%# ide I'm using (NetBeans) didn't have a bizarro bug > where you never know if a commit will work or not. I've had it raised as an > issue for over a week, and I'm finally getting to the point where the right > guys @ netbeans are taking it seriously. Believe me it pisses me off more > than you.... Not to be a jerk about it, but why don't you just commit from the command line? I use IDEA and _love_ the CVS integration for add, remove, update, et cetera, but I still do all my commits from the command line for the exact reason you mention above -- you never know if it will work or not. And it might make it easier to aggregate some of your commits =] -- jt -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
