[MacPorts] #26179: bzflag: consistent whitespace, please
#26179: bzflag: consistent whitespace, please -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: phw@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: bzflag -------------------------------------+-------------------------------------- The bzflag portfile uses inconsistent indentation. Most of the portfile uses tabs at 8 spaces per tab for indentation lining up at column 20 (meaning there are also spaces thrown in there), but the checksum lines use tabs at 4 spaces per tab lining up at column 20. And the livecheck lines use 8-space tabs lining up at column 24. Please switch to a consistent indentation style using only spaces. Adding the standard MacPorts modeline would also be a good idea at that point. Attached is one possible fix. -- Ticket URL: <http://trac.macports.org/ticket/26179> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26179: bzflag: consistent whitespace, please --------------------------------------+------------------------------------- Reporter: ryandesign@… | Owner: phw@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: bzflag | --------------------------------------+------------------------------------- Changes (by phw@…): * status: new => closed * resolution: => fixed Comment: Resolved in revision 77966 -- Ticket URL: <https://trac.macports.org/ticket/26179#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26179: bzflag: consistent whitespace, please --------------------------------------+------------------------------------- Reporter: ryandesign@… | Owner: phw@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: bzflag | --------------------------------------+------------------------------------- Comment(by ryandesign@…): If instead of "revision 77966" you write "r77966", Trac will make a helpful link out of it. Note that it is better to make whitespace changes in a separate commit from functional changes; that way, whitespace commits can be ignored by people reviewing commits, and in functional commits, the changes are easy to see. -- Ticket URL: <https://trac.macports.org/ticket/26179#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts