Dan Zwell <dzwell@xxxxxxxxx> wrote: > Sorry, that I didn't read the document on submitting patches before > this. I will make the other changes you mention and re-send this in > the proper formatting. I really should have pointed you to Documentation/SubmittingPatches when I responded to your email in the first place. Sorry I didn't do that. Looks like you already found it though so good. > > > +Note: these are not the same colors/attributes that the > > > +rest of git supports, but are specific to git-add--interactive. > > > > This is a problem in my opinion. Why can't it match the same > > names that the C code recognizes? What if we one day were to > > see git-add--interactive.perl converted to C? How would we then > > reconcile the color handling at that point in time? > > Makes sense. I am adding a bit of code to parse git color strings into > perl color strings (so the user can use the same color names as with > the rest of git). I know this is a small change, but I'm learning perl > as I go, and I have exams this week, so it will take at least a day or > two. I will fix the color issue, and send a properly formatted and > signed-off patch. (Yes, I do agree to the Developer's Certificate of > Origin wrt to this patch.) > > Thanks for your patience, Thanks for working on this. I played around with your patch tonight and although I use git-gui more often than `git add -i` for hunk manipulation I really preferred your colorized version of git-add -i over the non-colorized one. So I'm looking forward to seeing the final result of this and getting it into the main tree. Of course there is also no rush to getting your change in. We don't have any sort of release deadlines. So don't stress out about it too much. :) -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
