Re: [Nagios-devel] OT Re: Patch RFC - Nagios 3.2 - permanently
Posted: Tue Nov 03, 2009 10:11 am
On 11/03/2009 09:48 AM, Thomas Guyot-Sionnest wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/11/09 05:13 PM, Hendrik Baecker wrote:
>>
>> Off Topic
>>
>> 1st: *ouch*
>> 2nd: AFAIR, there were some discussions in the past to pipe the code
>> through intend... guess it's stale for the moment.
>> http://wiki.nagios.org/index.php/Nagios ... Code_style
>>
>> So... the style has a name
>
> Considering that the repo should move to Git soon intend could possibly
> be run trough git filter-branch when setting up Git. That should be easy
> and if it works will result in all code history to be (hopefully)
> properly intended.
>
Yup. This is a task of mine. I've got the repository set up at
devteams.nagios.org, but haven't synced it to sourceforge yet, as I'm
still not sure how to enable sourceforge cvs access alongside the git
repository. Especially in view of the fact that we'll want to rename
the tags (from nagios-2_1 to nagios-2.1) in git, and that we'd like
to run indent on the history, as you say.
Also, I'm having a spot of trouble bending the indent program to my
will. It seems buggy in recognizing typecasts and insist on indenting
some of them differently. I'm of half a mind to hack sparse to take care
of it, or simply write a very small c-program that supports only one
style but does The Right Thing for everything.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/11/09 05:13 PM, Hendrik Baecker wrote:
>>
>> Off Topic
>>
>> 1st: *ouch*
>> 2nd: AFAIR, there were some discussions in the past to pipe the code
>> through intend... guess it's stale for the moment.
>> http://wiki.nagios.org/index.php/Nagios ... Code_style
>>
>> So... the style has a name
>
> Considering that the repo should move to Git soon intend could possibly
> be run trough git filter-branch when setting up Git. That should be easy
> and if it works will result in all code history to be (hopefully)
> properly intended.
>
Yup. This is a task of mine. I've got the repository set up at
devteams.nagios.org, but haven't synced it to sourceforge yet, as I'm
still not sure how to enable sourceforge cvs access alongside the git
repository. Especially in view of the fact that we'll want to rename
the tags (from nagios-2_1 to nagios-2.1) in git, and that we'd like
to run indent on the history, as you say.
Also, I'm having a spot of trouble bending the indent program to my
will. It seems buggy in recognizing typecasts and insist on indenting
some of them differently. I'm of half a mind to hack sparse to take care
of it, or simply write a very small c-program that supports only one
style but does The Right Thing for everything.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]