On 18.9.2012, at 15:22, Bastien wrote: > Hi Jambunathan, > > Jambunathan K <kjambunat...@gmail.com> writes: > >> Please ask for clarification and politely indicate that a change may >> have to be reverted. > > Sorry that I reverted this one too hastily and without warning. > >> Instead of the commit being wrong, is it possible that >> changes were incomplete. > > I understand. > > What would be helpful would be some comment in the commit telling > that the change is part of a bigger change that is not yet committed. > > But I think we should try to avoid this: the whole point of using git > is to commit changes only if they are complete.
Hi Bastien, I think this should be to *merge* (and push) only complete changes. At least this is what I think - git allows you to commit often while making changes. Actually, I think you agree, your next paragraph says as much. - Carsten > A "change" can be a > commit or a set of commits, but let's try to push changes only when > they are complete. > > I know this is not always easy, and I'm not lecturing here, I'm just > sharing directions I try to follow myself. > > Thanks, > > -- > Bastien >
