Hi guys, first let's say that I really appreciate the job you're doing. So thanks to all of you. And kindly consider the little updates that I am requesting. It's just a whitespace cleaning and some indentations added in the code. Regards,
Bitcoin's cleanner #246
pull canercandan wants to merge 3 commits into bitcoin:master from canercandan:bitcoin changing 42 files +20015 −19927-
canercandan commented at 3:15 PM on May 20, 2011: none
-
* whitespaces cleanup defe363c1f
-
* indentations 9957f8eea8
-
* indentations 01a5c3b41c
-
TheBlueMatt commented at 4:12 PM on May 20, 2011: member
Hm, not sure why we need to change our indentation format. It is one of the most common types of indentation/code format (though possibly some different bracket positioning is more common).
Though some of the removal of random spaces at the end of lines and cleaning up number of spaces at various points could be done.
-
canercandan commented at 4:29 PM on May 20, 2011: none
I thought that no standard has been used regarding the indentation of code, so you're right we don't have to take this commit in account even if I like a bit more this style in my Emacs ;)
-
sipa commented at 1:57 PM on May 21, 2011: member
Removing spaces and cleaning up is fine, but the project has well-defined code style rules, which I don't think should be changed without discussion.
-
canercandan commented at 8:19 PM on May 21, 2011: none
you are absolutely right.
-
jaromil commented at 9:04 AM on May 29, 2011: contributor
the indentation and code style was declared and we are all already adapting to it, why change it?
i'm also disagreeing with the "whitespace cleanup": while that is an easy trick using the emacs extension, it does provoke unnecessary conflicts when merging master into branches.
ultimately i don't see any good reason why to pull this req.
-
canercandan commented at 11:21 AM on May 29, 2011: none
jaromil, are there any rules regarding the indentation and code style defined by the community of developer around the project ? If yes can any one give me some directives to respect these rules in the future ?
Thanks.
-
TheBlueMatt commented at 11:26 AM on May 29, 2011: member
There should be in docs/coding.txt
-
canercandan commented at 12:21 PM on May 29, 2011: none
Thanks.
-
jaromil commented at 10:36 PM on May 30, 2011: contributor
i see one good thing in this operation, but then it should split from all the rest and be proposed as a standalone pull request: in addition to the changes you mentioned, you have also added #ifndef / #define to headers, a common practice to avoid multiple inclusion and redeclarations. as that would be a good step towards getting rid of the headers.h insanity, it'd be good to have it IMHO. but then again, as a separate pull request plz.
-
canercandan commented at 8:32 AM on June 1, 2011: none
I will separate the change you mentioned from the rest of the pull. If there is anything else to keep, go ahead ;)
-
jgarzik commented at 4:10 AM on June 7, 2011: contributor
we have a metric ton of pending patches, and unfortunately this pull request is very low priority compared to other changes which change a lot of bitcoin code. whitespace diffs tend to require merging and rebasing downstream for very little value.
So this pull request is, and will continue to become, out of date. Other changes should definitely go into separate pull requests.
- jgarzik closed this on Jun 7, 2011
- dexX7 referenced this in commit a099a24d2a on Jan 24, 2015
- deadalnix referenced this in commit 141f0871e6 on May 10, 2017
- lateminer referenced this in commit 0b56078907 on Dec 9, 2017
- attilaaf referenced this in commit 306f9baca8 on Jan 13, 2020
- cryptapus referenced this in commit a8ad5a92fd on May 3, 2021
- cryptapus referenced this in commit 15a5bd4a27 on May 3, 2021
- cryptapus referenced this in commit 3961b00136 on May 3, 2021
- cryptapus referenced this in commit dd908da96b on May 3, 2021
- rajarshimaitra referenced this in commit 5da9deb66f on Aug 5, 2021
- DrahtBot locked this on Sep 8, 2021