# [EGIT] How to deal with important modifications 4 messages from 2009-03-28 to 2009-03-30. Participants: Yann Simon, Ferry Huberts (Pelagic), Robin Rosenberg, Shawn O. Pearce. Thread: https://gitlist.dev/t/18603 ## Yann Simon, 2009-03-28 17:32 Subject: [EGIT] How to deal with important modifications Message-ID: <1238261528.6971.10.camel@localhost> URL: https://gitlist.dev/e/1238261528.6971.10.camel%40localhost ``` Hi, I am working on the synchronization view. It is not 100% functional yet. The view is not updated when a local file is modified for example. As the modifications are getting important, I was wondering how to deal with it. Should I continue my work an send all the patches when finished? To have an overview of the modifications: http://github.com/yanns/egit/commit/18c4a928d53345802a8c9641dcb2d457ebbe2cbc http://github.com/yanns/egit/commit/9fab398fa1b7b6efa9532b3c09e5bcfcc8bb9419 Or should I begin to send patches, but by not activating the function yet? (It could be a way to have other people to help contributing.) Yann ``` ## Ferry Huberts (Pelagic), 2009-03-28 22:44 Subject: Re: [EGIT] How to deal with important modifications Message-ID: <49CEA861.4070700@pelagic.nl> URL: https://gitlist.dev/e/49CEA861.4070700%40pelagic.nl In-Reply-To: <1238261528.6971.10.camel@localhost> ``` Yann Simon wrote: > Hi, > > I am working on the synchronization view. It is not 100% functional yet. > The view is not updated when a local file is modified for example. > As the modifications are getting important, I was wondering how to deal > with it. Should I continue my work an send all the patches when > finished? > > To have an overview of the modifications: > http://github.com/yanns/egit/commit/18c4a928d53345802a8c9641dcb2d457ebbe2cbc > http://github.com/yanns/egit/commit/9fab398fa1b7b6efa9532b3c09e5bcfcc8bb9419 > > Or should I begin to send patches, but by not activating the function > yet? > (It could be a way to have other people to help contributing.) > > Yann Yann, I was asking myself the same questions about my work on ignores and chose to send it out early, being half completed. Don't know if that was right, did not receive feedback yet, but it's only been 2 days with Eclipsecon wrapping up on friday. If you keep a seperate changeset in which you activate your work and split up the changesets in manageable pieces it's easier for others to review your work and comment on it. Love to see your work though. Having the sync view available for git would be a major plus. I proposed something simpler on the wiki: a 'pending changes' window. But if you have the complete sync view that's wonderful. my 2 cents :-) Ferry ``` ## Robin Rosenberg, 2009-03-29 09:45 Subject: Re: [EGIT] How to deal with important modifications Message-ID: <200903291145.06135.robin.rosenberg.lists@dewire.com> URL: https://gitlist.dev/e/200903291145.06135.robin.rosenberg.lists%40dewire.com In-Reply-To: <49CEA861.4070700@pelagic.nl> ``` lördag 28 mars 2009 23:44:49 skrev "Ferry Huberts (Pelagic)" : > Yann Simon wrote: > > Hi, > > > > I am working on the synchronization view. It is not 100% functional yet. > > The view is not updated when a local file is modified for example. > > As the modifications are getting important, I was wondering how to deal > > with it. Should I continue my work an send all the patches when > > finished? > > > > To have an overview of the modifications: > > http://github.com/yanns/egit/commit/18c4a928d53345802a8c9641dcb2d457ebbe2cbc > > http://github.com/yanns/egit/commit/9fab398fa1b7b6efa9532b3c09e5bcfcc8bb9419 > > > > Or should I begin to send patches, but by not activating the function > > yet? > > (It could be a way to have other people to help contributing.) > > > > Yann > Yann, > > I was asking myself the same questions about my work on ignores and > chose to send it out early, being half completed. Don't know if that was > right, did not receive feedback yet, but it's only been 2 days with > Eclipsecon wrapping up on friday. That's not the reason you haven't received a response. Basically, the larger a set of patches is, more time is needed. > If you keep a seperate changeset in which you activate your work and > split up the changesets in manageable pieces it's easier for others to > review your work and comment on it. Indeed. Small patches can be reviewed more quickly if they introduce well defined changes and especially good is if they make sense of their own. Think about how you would like the changes presented if you were to review them without knowing anything in advance. -- robin ``` ## Shawn O. Pearce, 2009-03-30 04:30 Subject: Re: [EGIT] How to deal with important modifications Message-ID: <20090330043009.GT23521@spearce.org> URL: https://gitlist.dev/e/20090330043009.GT23521%40spearce.org In-Reply-To: <200903291145.06135.robin.rosenberg.lists@dewire.com> ``` Robin Rosenberg wrote: > l?rdag 28 mars 2009 23:44:49 skrev "Ferry Huberts (Pelagic)" : > > > > I was asking myself the same questions about my work on ignores and > > chose to send it out early, being half completed. Don't know if that was > > right, did not receive feedback yet, but it's only been 2 days with > > Eclipsecon wrapping up on friday. > > That's not the reason you haven't received a response. Basically, the larger > a set of patches is, more time is needed. Yup. I plan to block off time to look at the patches tomorrow. The bigger it is, the more likely it gets pushed off a few days, until I can block off a seemingly large enough amount of time to give it a complete reading. -- Shawn. ```