From 6c598c78bd17642d731cf57b8369cc794f64ba2f Mon Sep 17 00:00:00 2001 From: Luca Barbieri Date: Thu, 23 Sep 2010 13:44:22 +0200 Subject: d3d1x: normalize whitespace --- src/gallium/state_trackers/d3d1x/docs/coding_style.txt | 1 - 1 file changed, 1 deletion(-) (limited to 'src/gallium/state_trackers/d3d1x/docs') diff --git a/src/gallium/state_trackers/d3d1x/docs/coding_style.txt b/src/gallium/state_trackers/d3d1x/docs/coding_style.txt index a644a1323f3..fb09417eac6 100644 --- a/src/gallium/state_trackers/d3d1x/docs/coding_style.txt +++ b/src/gallium/state_trackers/d3d1x/docs/coding_style.txt @@ -6,7 +6,6 @@ The goal of these guidelines is to allow as much freedom as possible, while keep - Align multiline statements with an additional extra tab before each continuation line - Keep in mind that people can program with proportional fonts: hence, don't attempt to align anything not at the start of the line, since it's impossible - In general, there should never be two consecutive spaces in the source code -- As a special exception, [in] and __in annotations are followed by two spaces to align them with [out] and __out if displayed with a fixed size font. This may be revisited. - There is no strict limit on line length, but try to not make lines too long, and insert a line break where it looks good * Language/platform features -- cgit v1.2.3