On Thu, 2 Mar 2017 17:34:11 +0100
Carl Eugen Hoyos wrote:
> 2017-03-01 13:31 GMT+01:00 wm4 :
> > On Wed, 1 Mar 2017 13:06:29 +0100
> > Carl Eugen Hoyos wrote:
> >
> >> 2017-03-01 12:36 GMT+01:00 wm4 :
> >> > On Wed, 1 Mar 2017 12:20:10 +0100
> >> > Carl Eugen Hoyos wrote:
> >> >
> >> >> 2
2017-03-01 13:31 GMT+01:00 wm4 :
> On Wed, 1 Mar 2017 13:06:29 +0100
> Carl Eugen Hoyos wrote:
>
>> 2017-03-01 12:36 GMT+01:00 wm4 :
>> > On Wed, 1 Mar 2017 12:20:10 +0100
>> > Carl Eugen Hoyos wrote:
>> >
>> >> 2017-02-25 15:59 GMT+01:00 wm4 :
>> >> > I'm documenting existing practice.
>> >>
>>
On Thu, 2 Mar 2017 12:44:57 +0100
Michael Niedermayer wrote:
> On Wed, Mar 01, 2017 at 01:31:02PM +0100, wm4 wrote:
> > On Wed, 1 Mar 2017 13:06:29 +0100
> > Carl Eugen Hoyos wrote:
> >
> > > 2017-03-01 12:36 GMT+01:00 wm4 :
> > > > On Wed, 1 Mar 2017 12:20:10 +0100
> > > > Carl Eugen Hoyos
On Wed, Mar 01, 2017 at 01:31:02PM +0100, wm4 wrote:
> On Wed, 1 Mar 2017 13:06:29 +0100
> Carl Eugen Hoyos wrote:
>
> > 2017-03-01 12:36 GMT+01:00 wm4 :
> > > On Wed, 1 Mar 2017 12:20:10 +0100
> > > Carl Eugen Hoyos wrote:
> > >
> > >> 2017-02-25 15:59 GMT+01:00 wm4 :
> > >> > I'm documenti
On Wed, 1 Mar 2017 13:06:29 +0100
Carl Eugen Hoyos wrote:
> 2017-03-01 12:36 GMT+01:00 wm4 :
> > On Wed, 1 Mar 2017 12:20:10 +0100
> > Carl Eugen Hoyos wrote:
> >
> >> 2017-02-25 15:59 GMT+01:00 wm4 :
> >> > I'm documenting existing practice.
> >>
> >> > -@subheading Always wait long eno
2017-03-01 12:36 GMT+01:00 wm4 :
> On Wed, 1 Mar 2017 12:20:10 +0100
> Carl Eugen Hoyos wrote:
>
>> 2017-02-25 15:59 GMT+01:00 wm4 :
>> > I'm documenting existing practice.
>>
>> > -@subheading Always wait long enough before pushing changes
>> > +@subheading Always wait long enough before pushing
On Wed, 1 Mar 2017 12:20:10 +0100
Carl Eugen Hoyos wrote:
> 2017-02-25 15:59 GMT+01:00 wm4 :
> > I'm documenting existing practice.
>
> > -@subheading Always wait long enough before pushing changes
> > +@subheading Always wait long enough before pushing changes to code
> > actively maintained
2017-02-25 21:23 GMT+01:00 Marton Balint :
> Of course, I could just subscribe to csvlog as well
I was under the impression that if you want commit rights,
you are required to be subscribed to -cvslog.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-de
2017-02-25 19:35 GMT+01:00 Marton Balint :
> Instead of this, I'd prefer all patches on the ML.
This would mean we changed from a policy that we successful
applied for over a decade to a policy of which we - to the best
of my knowledge - know that it does not work well.
> Exceptions can be OKish
2017-02-25 16:03 GMT+01:00 Ivan Kalvachev :
> I do prefer all the code to go though the maillist.
> Even trivial changes.
This is not how we have done it for more than a decade
and I am against changing our (extremely successful) practice.
Carl Eugen
_
2017-02-25 15:59 GMT+01:00 wm4 :
> I'm documenting existing practice.
> -@subheading Always wait long enough before pushing changes
> +@subheading Always wait long enough before pushing changes to code actively
> maintained by others
I suspect this is missing an exception for security issues if
On Sat, 25 Feb 2017 21:23:27 +0100 (CET)
Marton Balint wrote:
> On Sat, 25 Feb 2017, Rostislav Pehlivanov wrote:
>
> > On 25 February 2017 at 18:35, Marton Balint wrote:
> >
> >>
> >> On Sat, 25 Feb 2017, wm4 wrote:
> >>
> >> I'm documenting existing practice.
> >>>
> >>> I'm pulling the "6
On Sat, Feb 25, 2017 at 11:47 PM, Rostislav Pehlivanov
wrote:
>>
>> This is the way it has been done for years and its the way the project has
>>> been able to move as rapidly as it has. That would slow down anything
>>> large
>>> from being developed in the codebase, like encoders or decoders for
On 25 February 2017 at 20:23, Marton Balint wrote:
>
> On Sat, 25 Feb 2017, Rostislav Pehlivanov wrote:
>
> On 25 February 2017 at 18:35, Marton Balint wrote:
>>
>>
>>> On Sat, 25 Feb 2017, wm4 wrote:
>>>
>>> I'm documenting existing practice.
>>>
I'm pulling the "6 months" timeout out
On Sat, Feb 25, 2017, at 11:23 AM, Marton Balint wrote:
>
> I only want to have a chance to review before patches got pushed. I am
> not
> saying we should explicitly demand a review for each patch. So this
> normally should only cause any developer an additional sent email to the
> ML and 1-2 d
On Sat, 25 Feb 2017, Rostislav Pehlivanov wrote:
On 25 February 2017 at 18:35, Marton Balint wrote:
On Sat, 25 Feb 2017, wm4 wrote:
I'm documenting existing practice.
I'm pulling the "6 months" timeout out of my ass, but I think it's
pretty suitable.
---
[...]
This is the way it has
On 25 February 2017 at 18:35, Marton Balint wrote:
>
> On Sat, 25 Feb 2017, wm4 wrote:
>
> I'm documenting existing practice.
>>
>> I'm pulling the "6 months" timeout out of my ass, but I think it's
>> pretty suitable.
>> ---
>> doc/developer.texi | 10 +-
>> 1 file changed, 9 insertions(+
On Sat, 25 Feb 2017, wm4 wrote:
I'm documenting existing practice.
I'm pulling the "6 months" timeout out of my ass, but I think it's
pretty suitable.
---
doc/developer.texi | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/developer.texi b/doc/developer.texi
ind
On 25 February 2017 at 14:59, wm4 wrote:
> I'm documenting existing practice.
>
> I'm pulling the "6 months" timeout out of my ass, but I think it's
> pretty suitable.
> ---
> doc/developer.texi | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/doc/developer.texi
On Sat, 25 Feb 2017 17:03:58 +0200
Ivan Kalvachev wrote:
> On 2/25/17, wm4 wrote:
> > I'm documenting existing practice.
> >
> > I'm pulling the "6 months" timeout out of my ass, but I think it's
> > pretty suitable.
> > ---
> > doc/developer.texi | 10 +-
> > 1 file changed, 9 insertio
On 2/25/17, wm4 wrote:
> I'm documenting existing practice.
>
> I'm pulling the "6 months" timeout out of my ass, but I think it's
> pretty suitable.
> ---
> doc/developer.texi | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/doc/developer.texi b/doc/developer.te
I'm documenting existing practice.
I'm pulling the "6 months" timeout out of my ass, but I think it's
pretty suitable.
---
doc/developer.texi | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index dbe1f5421f..41551498ad 100644
-
22 matches
Mail list logo
