[Mono-dev] [Fwd: [Mono-patches] r106626 - in trunk/mcs/class/System.Configuration: . System.Configuration Test/System.Configuration Test/standalone]

M. David Peterson xmlhacker at gmail.com
Fri Jun 27 04:19:29 EDT 2008


On Thu, Jun 26, 2008 at 12:03 PM, Gert Driesen <gert.driesen at telenet.be>

> I'm not deliberately ignoring your or anyone else's advice. Perhaps my idea
> of trivial changes is different than yours, definitely if a very large part
> of those changes is covered by unit tests. Next time, I'll flood mono-dev
> with small patches ;-)

For what it's worth, have you considered creating a local GIT repository
that mirrors the SVN repository and use this to make local atomic commits as
suggested by Jb, but doing so in a way that allows you to make a larger
grouped commit to SVN such that you can retain the commit history?  This
would also allow nicely for creating local branches specific to each
extended or non-mainstream feature as well as related unit tests you might
be working on and, when you feel its potentially ready for commit, submit a
patch to the dev list for discussion.  This ensures that the primary
maintainer of the given code maintains control while at the same time
allowing you the ability to move forward with your changes via your local
branch if for some reason it's felt the changes are not appropriate for the
main branch.

I assume you've seen the reference on how to go about the git-svn process
for the Mono SVN repository, but just in case >
http://www.mono-project.com/GitSVN <


M. David Peterson
Co-Founder & Chief Architect, 3rd & Urban, LLC
Email: m.david at 3rdandUrban.com | m.david at amp.fm
Mobile: (206) 999-0588
http://3rdandUrban.com | http://amp.fm |
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080627/7c14c550/attachment.html 

More information about the Mono-devel-list mailing list