Re: Patch merged in master branch for coding policy and patch submission

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>
>> What do we do whan the code surrounding the change has tabs? Should we
>> adapt to the local style, or change everything?
>
> It ignores changes in certain types of files, but .c and .h shouldn't have tabs
>

So there are two possibilities

- Whitespace
- erroneous spaces between functions
- Malformed sign-off
- Wrong jenkins URL

are hard errors and you wouldn't be allowed to submit. NOTE: yes it
makes sure to ignore Markdown files which require white-space as their
return character.

Majority of them are treated as "Warning", like "tabs" so which can be
safely ignored or feel to fix them, a choice is given (y/n)

-- 
Religious confuse piety with mere ritual, the virtuous confuse
regulation with outcomes
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux