Granularity of Check-Ins

Coordinator
Jan 6, 2008 at 2:11 AM
As you might have noticed, I made a number of check-ins tonight.

I made a number of changes that were affecting different issues/areas of code.
I performed check-ins in the same way that I would at work, based on feature affected.

What is the usual pattern for this in an OSS project?
Should I just check in all the files at once and have a large comment explaining all of the changes? Or is what I have done the right way, commenting each defect or feature addressed?
Developer
Jan 14, 2008 at 9:04 AM
This is my first OSS project to work on, so I don't know of any usual patterns. But like you I tend to group my check-ins by work item or feature instead of lumping them all together.
Jan 24, 2008 at 12:29 PM

HolisticDeveloper wrote:
This is my first OSS project to work on, so I don't know of any usual patterns. But like you I tend to group my check-ins by work item or feature instead of lumping them all together.


I guess if the code changes are small it will be quick to work out which change relates to which feature/fix. Otherwise if there are significant changes it could get confusing.

my 2c