On Fri, Feb 17, 2012, at 14:13, Juliusz Chroboczek wrote:
> > git pull git://github.com/wmanley/polipo.git documentation
>
> It would be helpful if you could avoid putting multiple unrelated
> changes into a single commit -- it would make cherry-picking easier.
I assume that you're refering to the fact that I added const in the same
commit as adding documentation. I added const as a means of documenting
whether the parameters were input or output parameters so I suppose I
didn't consider these changes to be unrelated, but I see that perhaps it
would have been better to commit the const changes before the
documentation changes (the doc changes depend on the const changes but
not vice-versa).
>From your email I take it that you prefer to cherry-pick rather than to
merge. Is this the case? I've been trying to make my patches as easy
to merge as possible by basing each branch off a common branch point
(i.e. the 1.0.4.1 release). If you're cherry picking anyway maybe I'll
worry about this less.
I've split the commits as above. You can find them at
git pull g...@github.com:wmanley/polipo.git documentation2
Thanks
Will
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Polipo-users mailing list
Polipo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/polipo-users
