On Wed, 13 Mar 2019 01:02:50 +0100 Samuel Thibault <samuel.thiba...@gnu.org> wrote:
> That looks nice, indeed, but submitting the final local.css file makes > it hard for us to review each piece of change. It'd be a lot easier > for us to look at it and commit what we agree on, if you submitted a > patch series. > > A hundred tiny changes would be tedious to review, but a big one > change is complex to review as well. A good middleground is just to > be found :) > > Samuel (If this shows up in a new thread, I'm sorry. I have no idea how mailing lists work) Sounds good. I can upload a series of patches, such as: News section changes Sidebar changes Header changes Mobile site addition and miscellaneous modifications. Each of these changes should be decently small in size. How should I go about posting these? For each patch I can make a copy of the original (currently active) CSS file and modify them so each patch has the same "old" file, but with different sections changed. Or I can just upload a very small CSS file per patch, containing nothing other than the modified code (maybe a file upload isn't even necessary?)
