Skip to Content.
Sympa Menu

devel - Re: [sympa-developpers] Release plans for 2014

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: IKEDA Soji <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-developpers] Release plans for 2014
  • Date: Thu, 16 Jan 2014 22:53:47 +0900

Hi,

As current sources didn't consider line width, simple perltidy'ing
doesn't give satisfying output. So I extended perltidy. Attached
script will be used for my work on Friday.

# Thus, reformatting became reproducible work.
# I'm planning to write a script to relpay reordering work Guillaume
# did manually.

Regards,

--- Soji

On Mon, 13 Jan 2014 14:18:51 +0100
Guillaume Rousse <address@concealed> wrote:

> > 2. Reformatting sources shall be made in this week.

> > 2. Reformatting sources shall be made in this week.
> >
> > Currently, we must work on three branches: 6.1, 6.2 and trunk.
> > Keeping these is sync will become more and more difficult due to
> > confused format.
> >
> > Even if indentation, line folding or spacing are so nonsense, we
> > hesitate to fix them. Because, such fixes may make comparison
> > between revisions and/or branches difficult.
> > Thus, sources will become more and more unreadable and unmaitenable.
> >
> > To leave such dead end, I will apply perltidy to all Perl sources
> > in all three branches, 6.1, 6.2 and trunk.
> It doesn't make much sense to reformat a maintainance branch such as
> 6.1, with already 17 releases in the wild. In order to make 6.2/6.1
> comparaison easier, it will make comparaison between 6.1.x and 6.1.y
> more difficult...
>
> If you really need to compare 6.1 and 6.2, I think diff option
> --ignore-all-space should probably be enough.
>
> > - This is not a proposal. I'm notifying.
> >
> > If you are currently making big changes on your local checkout,
> > I'd like to wait for it being committed. Please inform me.
> > Otherwise, I will make reformatting in this week.
> I'm working on file content/properties/headers this afternoon, that's
> all for me.
>
> > - Reformatting will not make codes unstable.
> >
> > - Since there are various preferences on coding style, perltidy
> > also have various options. I'll use attached .perltidyrc that
> > contains options with less objections by sympa-developpers folks.
> >
> > - Though Guillaume doesn't want to use perltidy, this is useful for
> > us including him: He can present which style he is wished by
> > correcting styles on trunk. And anyway, uniform reformatting will
> > reduce Guillaume's work to get desired style.
> Fine with me.
>
> --
> Guillaume Rousse
> INRIA, Direction des systèmes d'information
> Domaine de Voluceau
> Rocquencourt - BP 105
> 78153 Le Chesnay
> Tel: 01 39 63 58 31
>


--
株式会社 コンバージョン セキュリティ&OSSソリューション部 池田荘児
〒231-0004 神奈川県横浜市中区元浜町3-21-2 ヘリオス関内ビル7F
e-mail address@concealed TEL 045-640-3550
http://www.conversion.co.jp/

Attachment: custom_perltidy.pl
Description: Perl program




Archive powered by MHonArc 2.6.19+.

Top of Page