R: [Mono-devel-list] Analyzing Subversion logs
lists at paolomarini.it
Wed Jan 12 10:39:19 EST 2005
Thanks for your time. Your reply to my question really opened my eyes.
Now I wonder if there exists a way to prepare offline a serie of commits
(each one with his own message and list of operations) and then run all of
Da: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]Per conto di Martin
Inviato: Wednesday, January 12, 2005 3:14 PM
A: Paolo Marini
Cc: mono-devel-list at lists.ximian.com
Oggetto: Re: [Mono-devel-list] Analyzing Subversion logs
On Wed, 2005-01-12 at 14:20 +0000, Paolo Marini wrote:
> At this point my questions are:
> - how can happen that an author performs two commits within a few
> (There are even commits only 1 second distant each other).
I'm doing this quite often when I'm in bug-fixing mode to save testing
Normally, you'd need to test your changes each time before committing.
Since this is very time consuming, I usually do some optimization when
fixing multiple simple bugs:
When I'm done with the first bug, I prepare the ChangeLog and log
message in my mcs/mcs directory, but instead of committing, I just make
a copy of the directory and move on to the next bug. When I'm done with
all the bugs, I run all the tests (may take about 20-25 minutes) and
then commit all my changes.
Another example is where people are working offline most of the time,
when they go online, they commit all their changes at once.
> - how do you usually perform a commit? Do you use the command line?
> RapidSVN? TortoiseSVN? Do this tools fragment a single commit into more
> commits? Why?
I'm using the command line.
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list