On Thu, 24 Oct 2019 15:33:04 +0200
Dmitry Vyukov wrote:
> On Thu, Oct 24, 2019 at 3:15 PM Steven Rostedt wrote:
> >
> > On Mon, 21 Oct 2019 18:39:18 +0300
> > Laurent Pinchart wrote:
>
> Purely theoretically let's consider that the changes do not
On Mon, 21 Oct 2019 18:39:18 +0300
Laurent Pinchart wrote:
> > I plan on continuing to develop mostly in email (I still send my patch
> > series via quilt!). But I'm not going to enforce everyone to continue
> > to use email if we can come up with a better way. I also want to make
> > sure that
On Tue, 15 Oct 2019 19:37:04 +0300
Laurent Pinchart wrote:
> But how far could we push this reasoning ? I've worked for a company
> whose corporate policy was that all source code had to be stored in SVN,
> not exception. I didn't reach the community to move kernel development
> away from git.
On Mon, 14 Oct 2019 16:56:58 -0400
"Theodore Y. Ts'o" wrote:
> So it's an extreme case, and is an example of corp e-mail insanity.
> The good news is that for companies that are really serious about
> working with upstream, they will roll out solutions for their own
> customers. For example,
On Mon, 14 Oct 2019 10:38:51 +1100
Daniel Axtens wrote:
> > It does bring up that any new workflow has to have security protocol
> > and threat model as part of its design.
>
> This is actually something that worries me about the patchwork
> workflow. Maintainers seem to trust the patchwork
On Fri, 11 Oct 2019 17:08:39 -0700
Stephen Hemminger wrote:
> Yes, my life is too short to fight with corporate stuff.
Heh, me too.
> There is a security first mindset which is good but gets in the way.
> The current generation of Internet standard mail protocols does not have
> enough
On Sat, 12 Oct 2019 08:54:22 +1000
Dave Airlie wrote:
> On Sat, 12 Oct 2019 at 08:34, Steven Rostedt wrote:
> >
> > On Fri, 11 Oct 2019 14:19:09 -0700
> > Stephen Hemminger wrote:
> >
> > > As someone who has to deal with a corporate busted mail s
On Fri, 11 Oct 2019 14:19:09 -0700
Stephen Hemminger wrote:
> As someone who has to deal with a corporate busted mail server.
> I agree mailing patches is a barrier to entry for many people today.
Hmm, and I wonder what company fosters so many issues with doing that
today? :-/
/me notices that
On Fri, 11 Oct 2019 11:32:54 -0700 (PDT)
David Miller wrote:
> From: Steven Rostedt
> Date: Fri, 11 Oct 2019 14:01:08 -0400
>
> > Thus, if we want people to send us their fixes, we better keep just
> > an email with a patch the lowest bar for entry.
>
> I a
On Fri, 11 Oct 2019 14:37:52 -0300
Mauro Carvalho Chehab wrote:
> I agree with Shuah. From time to time, we have one time only patch
> submission from people that just want to fix something that affects
> his machine.
I like to stress this point. There's been projects that I have written
a
On Thu, 10 Oct 2019 15:07:29 -0300
Mauro Carvalho Chehab wrote:
> Em Thu, 10 Oct 2019 10:41:50 -0400
> Konstantin Ryabitsev escreveu:
>
> > Hi, all:
> >
> > I would like to propose a new (large) feature to patchwork with the goal
> > to make the process of submitting a patch easier for
11 matches
Mail list logo
