Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-08-01 Thread Rafael J. Wysocki
On Thursday, August 01, 2013 12:16:40 PM Geert Uytterhoeven wrote: > On Tue, Jul 30, 2013 at 12:09 AM, Rafael J. Wysocki wrote: > > A single SOB tag usually means that the committer himself is the author of > > the change set and I don't see why this should be regarded as a bad thing in > > princi

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-08-01 Thread Geert Uytterhoeven
On Tue, Jul 30, 2013 at 12:09 AM, Rafael J. Wysocki wrote: > A single SOB tag usually means that the committer himself is the author of > the change set and I don't see why this should be regarded as a bad thing in > principle. Yes, it is technically possible for maintainers to "cheat", for > exa

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-31 Thread Rafael J. Wysocki
On Tuesday, July 30, 2013 10:47:31 PM H. Peter Anvin wrote: > On 07/29/2013 03:30 PM, Rafael J. Wysocki wrote: > > On Monday, July 29, 2013 02:17:34 PM John W. Linville wrote: > >> On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: > >> > >>> That said we have the same issue with co

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-30 Thread James Bottomley
On Tue, 2013-07-30 at 22:47 -0700, H. Peter Anvin wrote: > On 07/29/2013 03:30 PM, Rafael J. Wysocki wrote: > > On Monday, July 29, 2013 02:17:34 PM John W. Linville wrote: > >> On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: > >> > >>> That said we have the same issue with commi

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-30 Thread H. Peter Anvin
On 07/29/2013 03:30 PM, Rafael J. Wysocki wrote: > On Monday, July 29, 2013 02:17:34 PM John W. Linville wrote: >> On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: >> >>> That said we have the same issue with commits with just two SOB tags if >>> a maintainer applies a patch that

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Rafael J. Wysocki
On Monday, July 29, 2013 02:17:34 PM John W. Linville wrote: > On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: > > > That said we have the same issue with commits with just two SOB tags if > > a maintainer applies a patch that nobody has responded to. Are they going > > to > >

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Rafael J. Wysocki
On Monday, July 29, 2013 08:11:41 AM Jonathan Corbet wrote: > On Mon, 29 Jul 2013 15:10:33 +0200 > "Rafael J. Wysocki" wrote: > > > That actually is simple enough. > > > > Check out the Linus' master branch and do > > > > $ git log --ancestry-path --merges .. > > So I picked a recent, single-s

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Jason Cooper
On Mon, Jul 29, 2013 at 02:17:34PM -0400, John W. Linville wrote: > On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: > > > That said we have the same issue with commits with just two SOB tags if > > a maintainer applies a patch that nobody has responded to. Are they going > > t

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread John W. Linville
On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: > That said we have the same issue with commits with just two SOB tags if > a maintainer applies a patch that nobody has responded to. Are they going to > be regarded as "suspicious" too now? > > And what about trusting maintaine

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Jiri Kosina
On Mon, 29 Jul 2013, Paul Gortmaker wrote: > >> That actually is simple enough. > >> > >> Check out the Linus' master branch and do > >> > >> $ git log --ancestry-path --merges .. > > > > So I picked a recent, single-signoff patch mostly at random: > > > > 8ade62857ef77bdf639185410fbcd811aa7

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Paul Gortmaker
On 13-07-29 10:11 AM, Jonathan Corbet wrote: > On Mon, 29 Jul 2013 15:10:33 +0200 > "Rafael J. Wysocki" wrote: > >> That actually is simple enough. >> >> Check out the Linus' master branch and do >> >> $ git log --ancestry-path --merges .. > > So I picked a recent, single-signoff patch mostly at

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Jonathan Corbet
On Mon, 29 Jul 2013 15:10:33 +0200 "Rafael J. Wysocki" wrote: > That actually is simple enough. > > Check out the Linus' master branch and do > > $ git log --ancestry-path --merges .. So I picked a recent, single-signoff patch mostly at random: 8ade62857ef77bdf639185410fbcd811aa700cb2

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Rafael J. Wysocki
On Monday, July 29, 2013 09:03:57 AM Jason Cooper wrote: > On Mon, Jul 29, 2013 at 01:35:26PM +0200, Samuel Ortiz wrote: > > On Mon, Jul 29, 2013 at 06:40:32AM -0400, Jason Cooper wrote: > > > On Mon, Jul 29, 2013 at 12:31:37PM +0200, Jiri Kosina wrote: > > > > On Mon, 29 Jul 2013, Samuel Ortiz wro

Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

2013-07-29 Thread Rafael J. Wysocki
On Monday, July 29, 2013 12:31:37 PM Jiri Kosina wrote: > On Mon, 29 Jul 2013, Samuel Ortiz wrote: > > > - Developement process: Jon Corbet's article about our changelog raised > > one interesting question: How can we better track how single SOB > > patches are getting merged ? That actually