Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


On 05/21/2017 01:22 PM, Chris Sherlock wrote:
[...]
some of them I just didn’t notice the message on gerrit
[...]

I routinely add comments to already merged Gerrit changes, assuming that authors and reviewers will see the corresponding mails Gerrit sends out to them. If this is generally considered problematic, please let me know.

In terms of whitespacing causing issues in git archaeology, I thought git had options to help with this sort of thing, so if that’s a major issue then is there something stopping us from using this?

I don't think it's a major issue, just a minor nuisance (for stuff like seemingly randomly changing " {" to "\n{"). But even minor nuisances can pile up, and while git does have clever options to mitigate some of this, you need to remember to use those options, etc.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.