| Patch handling process and mylyn? [message #570917] |
Mon, 20 April 2009 01:44 |
 Alex Blewitt
Messages: 946
Registered: July 2009 |
Senior Member |
|
|
Having put a few patches together on Egit (and getting used to Git in
general, so please excuse any noob mistakes I make ...) I wanted to bring
up a difference between the way that patches are handled via the *git
review process and Eclipse.
Patches, as described in the SUBMITTING_PATCHES guide
(http://repo.or.cz/w/egit.git?a=blob;f=SUBMITTING_PATCHES;hb=HEAD)
involves emailing the patch to the current (2) maintainers, plus a Cc to
the (shared) *git mailing list. At some point, once they move past a
review, they presumably get folded upstream.
Eclipse, on the other hand, tends to use mail for discussions but patches
attached to bugs. Some projects even formalise it as part of the process
for comitters, not just contributions.
So I'm trying to find out what the plan is should things move to egit;
presumably, the developer discussions would move off the
git@vger.kernel.org mailing list and onto the eclipse.egit-dev mailing
list? And would patches start to flow via bug attachments instead?
Secondly, would we be able to take advantage of the nature of DVCS to
leverage applying patches in any way, like encouraging people to put
patches up via (say) github and then pulling in, or would that cause more
complications?
For those new to Eclipse/Mylyn, I've blogged about how to set up Google
Code from Mylyn at
http://alblue.blogspot.com/2009/04/google-code-and-mylyn-red ux.html and am
currently using this to track the issues I've raised/commented on. I'd be
interested if any of the existing or interested Egit participants find
this useful.
Alex
|
|
|
Powered by
FUDForum. Page generated in 0.02914 seconds
] 
Search
Help
Register
Login
Home
