Glynn:
> Any final comments before the entire source tree is
> reformatted?
Any thoughts on keeping the inter-branch svn merge effort low?
some sort of script that grabs the devbr6 copy of the modified .c file, runs
indent on it using these rules, then tries to commit it?
having to do a lot of merging by hand is a real demotivator, prone to human
error, and risks stuff not getting cross-committed (and then you can't easily
run diff to know that it [hasn't] has happened).
Q: With -br, is -bli1 needed so that things look like:
if (a == b) {
and not
if (a == b){
? (prefer the former)
for open braces functions, structs the { should not be indented 1 space from
the newline though..
maybe start with committing the change to one file and then put that up for
public review.. (as two mega-commits would be a pain)
Hamish
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
