+1 to a gradual perltidy.
In this case, we should add a comment on processed files like :
"#format by perltidy" ie
--
Fridolyn SOMERS
fridolyn.som...@gmail.com
Marsillargues - France
2012/3/10 Mason James
>
> On 2012-03-9, at 10:16 PM, Marcel de Rooy wrote:
>
> > +1 for a gradual perl tidy t
On 2012-03-9, at 10:16 PM, Marcel de Rooy wrote:
> +1 for a gradual perl tidy too
+1 to a gradual perltidy from me too
> >So, best to keep cleaning up incrementally, I think.A As we move from C4
> >to Koha, that'll be an opportunity to clean up all the modules
> >
> >-Ian
> >
> >
Thanks Paul, I guess we will go ahead and start submitting and hope some of
our submissions gets included. No strong reason to get this included in
3.8, other than us having to rebase multiple times.
In any case, here are some of the changes we want to submit at this stage,
some already have bugzi
unity.org
Objet : Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
Le 09/03/2012 13:36, Eric Bégin a écrit :
> Hello all,
>
> Have we considered using git's hooks for tidifying the code before
> checking it in, or even on the server, this would ensure that who
Hi to all,
- Messaggio originale -
> Da: "Paul Poulain"
> A: koha-devel@lists.koha-community.org
> Inviato: Giovedì, 8 marzo 2012 13:59:16
> Oggetto: [Koha-devel] Koha 3.8 release schedule & perltidy process
>
> Hello koha-devel,
>
> IMPORTANT
Le 09/03/2012 13:36, Eric Bégin a écrit :
> Hello all,
>
> Have we considered using git's hooks for tidifying the code before
> checking it in, or even on the server, this would ensure that whoever
> does the checkin, it will be tidified.
>
> Also, if we consider going with a global tidifying, a
rg
<mailto:koha-devel-boun...@lists.koha-community.org> im Auftrag
von Chris
>Nighswonger
> Gesendet: Do 08.03.2012 19:26
> An: Chris Cormack
>Cc: koha-devel@lists.koha-community.org
<mailto:koha-devel@lists.koha-community.org>
&
onden: donderdag 8 maart 2012 20:21
To: Chris Cormack
Cc: Fischer, Katrin; koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
Chris,
Right, with the colossal commit option, one could have to
1. Know the commit id of the change
2.
Le 09/03/2012 05:09, savitra sirohi a écrit :
> Hi Paul,
Hi Savitra,
> we have been caught off-guard by this schedule.
The schedule is the same as what we had for previous time-based-release.
I agree that my announcement could have be made a little bit earlier,
but you can, for future releases, co
Hi Paul, we have been caught off-guard by this schedule.
We have a lot of stuff to submit but March 23rd is too little time. If we
have 2 more weeks, we can get good stuff included. Possible?
Thanks,
Savitra Sirohi
Nucsoft OSS Labs
http://www.osslabs.biz
On Thu, Mar 8, 2012 at 6:29 PM, Paul Poul
n
> >
> >-UrsprA 1/4ngliche Nachricht-----
> > Von: koha-devel-boun...@lists.koha-community.org im Auftrag von
> Chris
> >Nighswonger
> >Gesendet: Do 08.03.2012 19:26
> >An: Chris Cormack
> >Cc: koha-devel
ts.koha-community.org im Auftrag von Chris
>Nighswonger
>Gesendet: Do 08.03.2012 19:26
> An: Chris Cormack
>Cc: koha-devel@lists.koha-community.org
>Betreff: Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
>
>2012/3/8 Ch
and Chris N. - I think what we would win does not
>> outweigh the loss of history.
>>
>> Katrin
>>
>> -Ursprüngliche Nachricht-
>> Von: koha-devel-boun...@lists.koha-community.org im Auftrag von Chris
>> Nighswonger
>> Gesendet: Do 08.03.2012 19
ty.org im Auftrag von Chris
> Nighswonger
> Gesendet: Do 08.03.2012 19:26
> An: Chris Cormack
> Cc: koha-devel@lists.koha-community.org
> Betreff: Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
>
>
> 2012/3/8 Chris Cormack
>
> > My counter proposal is tidy
@lists.koha-community.org
Betreff: Re: [Koha-devel] Koha 3.8 release schedule & perltidy process
2012/3/8 Chris Cormack
> My counter proposal is tidy as you go. Fix code as you touch it.
>
> With vim (and other editors) you can easily tidy a block, doing that as
> code is changed would
2012/3/8 Chris Cormack
> Doing it in one hit only makes this better if it is possible to have git
> blame ignore this commit.
>
>
>
Interestingly enough there seems to have been a patch submitted to GIT to
do just this sort of thing, but it got dropped along the way:
http://git.661346.n2.nabble.
2012/3/8 Chris Cormack
> My counter proposal is tidy as you go. Fix code as you touch it.
>
> With vim (and other editors) you can easily tidy a block, doing that as
> code is changed would be my preference.
>
I'd prefer a "pay-as-you-go" approach as well. We could simply require all
work to be
On Mar 9, 2012 6:41 AM, "Paul Poulain" wrote:
>
> Le 08/03/2012 18:30, Chris Cormack a écrit :
>
> > Doing it in one hit only makes this better if it is possible to have git
> > blame ignore this commit.
>
> I don't think it's possible.
>
> > I just want to go on record as disagreeing with this pl
Le 08/03/2012 18:30, Chris Cormack a écrit :
> Doing it in one hit only makes this better if it is possible to have git
> blame ignore this commit.
I don't think it's possible.
> I just want to go on record as disagreeing with this plan. But happy to
> abide by community decision I just reserve
On Mar 9, 2012 1:59 AM, "Paul Poulain" wrote:
>
> Hello koha-devel,
>
> I just updated the 3.8 release process with the schedule/planning of the
> release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8
>
> Here it is:
> March, 23th (1 month before the release) = feature freeze.
> April, 6th =
Le 08/03/2012 14:36, Marcel de Rooy a écrit :
> Hi Paul,
Hi Marcel,
> What is the exact procedure?
> All patches submitted before March 23 or signed-off before March 23
are candidates for the 3.8 release?
> If so, how do we separate them easily from the patches submitted
later? What is strong feat
-community.org
Onderwerp: [Koha-devel] Koha 3.8 release schedule & perltidy process
Hello koha-devel,
I just updated the 3.8 release process with the schedule/planning of the
release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8
Here it is:
March, 23th (1 month before the release) = feature fr
Hello koha-devel,
I just updated the 3.8 release process with the schedule/planning of the
release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8
Here it is:
March, 23th (1 month before the release) = feature freeze.
April, 6th = strong feature freeze, string freeze
April 20th = starting rel
23 matches
Mail list logo
