* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process @ 2017-11-03 21:10 Joseph Kogut 2017-11-04 18:53 ` Baruch Siach 2017-11-05 20:14 ` Peter Korsgaard 0 siblings, 2 replies; 8+ messages in thread From: Joseph Kogut @ 2017-11-03 21:10 UTC (permalink / raw) To: buildroot Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com> --- docs/manual/contribute.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt index a58945f395..8bbc2b9eb7 100644 --- a/docs/manual/contribute.txt +++ b/docs/manual/contribute.txt @@ -260,9 +260,9 @@ options that no longer exist or are no longer needed. If you are interested in getting notified of build failures and of further changes in the packages you added or modified, please add -yourself to the DEVELOPERS file. This should be done in a separate -patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more -information. +yourself to the DEVELOPERS file. This should be done in the same patch +creating or modifying the package. See xref:DEVELOPERS[the DEVELOPERS file] +for more information. ==== Preparing a patch series -- 2.15.0 ^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-03 21:10 [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process Joseph Kogut @ 2017-11-04 18:53 ` Baruch Siach 2017-11-04 22:14 ` Thomas Petazzoni 2017-11-05 20:14 ` Peter Korsgaard 1 sibling, 1 reply; 8+ messages in thread From: Baruch Siach @ 2017-11-04 18:53 UTC (permalink / raw) To: buildroot Hi Joseph, On Fri, Nov 03, 2017 at 02:10:53PM -0700, Joseph Kogut wrote: > Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com> > --- > docs/manual/contribute.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt > index a58945f395..8bbc2b9eb7 100644 > --- a/docs/manual/contribute.txt > +++ b/docs/manual/contribute.txt > @@ -260,9 +260,9 @@ options that no longer exist or are no longer needed. > > If you are interested in getting notified of build failures and of > further changes in the packages you added or modified, please add > -yourself to the DEVELOPERS file. This should be done in a separate > -patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more > -information. > +yourself to the DEVELOPERS file. This should be done in the same patch > +creating or modifying the package. See xref:DEVELOPERS[the DEVELOPERS file] > +for more information. Not sure about "or modifying". Mixing a DEVELOPERS update into a random package update does not always make sense. The manual only refers to new packages/boards. I suggest to drop this sentence entirely, and leave the details for the manual. baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il - ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-04 18:53 ` Baruch Siach @ 2017-11-04 22:14 ` Thomas Petazzoni 2017-11-05 6:07 ` Baruch Siach 2017-11-05 7:43 ` Peter Korsgaard 0 siblings, 2 replies; 8+ messages in thread From: Thomas Petazzoni @ 2017-11-04 22:14 UTC (permalink / raw) To: buildroot Hello, On Sat, 4 Nov 2017 20:53:05 +0200, Baruch Siach wrote: > > diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt > > index a58945f395..8bbc2b9eb7 100644 > > --- a/docs/manual/contribute.txt > > +++ b/docs/manual/contribute.txt > > @@ -260,9 +260,9 @@ options that no longer exist or are no longer needed. > > > > If you are interested in getting notified of build failures and of > > further changes in the packages you added or modified, please add > > -yourself to the DEVELOPERS file. This should be done in a separate > > -patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more > > -information. > > +yourself to the DEVELOPERS file. This should be done in the same patch > > +creating or modifying the package. See xref:DEVELOPERS[the DEVELOPERS file] > > +for more information. > > Not sure about "or modifying". Mixing a DEVELOPERS update into a random > package update does not always make sense. The manual only refers to new > packages/boards. I suggest to drop this sentence entirely, and leave the > details for the manual. Joseph is modifying the manual here, so I'm not sure what your last sentence means. However, I agree that doing the DEVELOPERS change in a patch just modifying the package is perhaps not desirable. When adding a new package, yes, definitely, the DEVELOPERS entry should be added as part of the same patch. However, when a package is being modified, that's a different story, and the package change should be in a separate patch than the DEVELOPERS addition. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-04 22:14 ` Thomas Petazzoni @ 2017-11-05 6:07 ` Baruch Siach 2017-11-05 8:55 ` Thomas Petazzoni 2017-11-05 7:43 ` Peter Korsgaard 1 sibling, 1 reply; 8+ messages in thread From: Baruch Siach @ 2017-11-05 6:07 UTC (permalink / raw) To: buildroot Hi Thomas, On Sat, Nov 04, 2017 at 11:14:27PM +0100, Thomas Petazzoni wrote: > On Sat, 4 Nov 2017 20:53:05 +0200, Baruch Siach wrote: > > > > diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt > > > index a58945f395..8bbc2b9eb7 100644 > > > --- a/docs/manual/contribute.txt > > > +++ b/docs/manual/contribute.txt > > > @@ -260,9 +260,9 @@ options that no longer exist or are no longer needed. > > > > > > If you are interested in getting notified of build failures and of > > > further changes in the packages you added or modified, please add > > > -yourself to the DEVELOPERS file. This should be done in a separate > > > -patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more > > > -information. > > > +yourself to the DEVELOPERS file. This should be done in the same patch > > > +creating or modifying the package. See xref:DEVELOPERS[the DEVELOPERS file] > > > +for more information. > > > > Not sure about "or modifying". Mixing a DEVELOPERS update into a random > > package update does not always make sense. The manual only refers to new > > packages/boards. I suggest to drop this sentence entirely, and leave the > > details for the manual. > > Joseph is modifying the manual here, so I'm not sure what your last > sentence means. Ah. For some reason I had the impression that this change is against the DEVELOPERS file itself. So let me rephrase my suggestion: I suggest to drop this sentence entirely, and leave the details for the DEVELOPERS manual section. > However, I agree that doing the DEVELOPERS change in a patch just > modifying the package is perhaps not desirable. When adding a new > package, yes, definitely, the DEVELOPERS entry should be added as part > of the same patch. However, when a package is being modified, that's a > different story, and the package change should be in a separate patch > than the DEVELOPERS addition. Agreed. baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il - ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-05 6:07 ` Baruch Siach @ 2017-11-05 8:55 ` Thomas Petazzoni 0 siblings, 0 replies; 8+ messages in thread From: Thomas Petazzoni @ 2017-11-05 8:55 UTC (permalink / raw) To: buildroot Hello, On Sun, 5 Nov 2017 08:07:49 +0200, Baruch Siach wrote: > > > Not sure about "or modifying". Mixing a DEVELOPERS update into a random > > > package update does not always make sense. The manual only refers to new > > > packages/boards. I suggest to drop this sentence entirely, and leave the > > > details for the manual. > > > > Joseph is modifying the manual here, so I'm not sure what your last > > sentence means. > > Ah. For some reason I had the impression that this change is against the > DEVELOPERS file itself. So let me rephrase my suggestion: > > I suggest to drop this sentence entirely, and leave the details for the > DEVELOPERS manual section. No, I think it is good to have this sentence in the "Adding a new package" section of the manual. Indeed new contributors are much more likely to read this section when contributing a new package than an obscure section specific to the DEVELOPERS file at the end of the manual. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-04 22:14 ` Thomas Petazzoni 2017-11-05 6:07 ` Baruch Siach @ 2017-11-05 7:43 ` Peter Korsgaard 2017-11-05 8:55 ` Thomas Petazzoni 1 sibling, 1 reply; 8+ messages in thread From: Peter Korsgaard @ 2017-11-05 7:43 UTC (permalink / raw) To: buildroot >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes: Hi, >> Not sure about "or modifying". Mixing a DEVELOPERS update into a random >> package update does not always make sense. The manual only refers to new >> packages/boards. I suggest to drop this sentence entirely, and leave the >> details for the manual. > Joseph is modifying the manual here, so I'm not sure what your last > sentence means. > However, I agree that doing the DEVELOPERS change in a patch just > modifying the package is perhaps not desirable. When adding a new > package, yes, definitely, the DEVELOPERS entry should be added as part > of the same patch. However, when a package is being modified, that's a > different story, and the package change should be in a separate patch > than the DEVELOPERS addition. I'm not sure it really matters much. A package change with a modification of DEVELOPERS would most likely be for a version bump of an unmaintained package where the person bumping wants to take over ownership, or similar. I don't think it is a problem to update DEVELOPERS together with the package in such cases, but keeping it separately is also fine. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-05 7:43 ` Peter Korsgaard @ 2017-11-05 8:55 ` Thomas Petazzoni 0 siblings, 0 replies; 8+ messages in thread From: Thomas Petazzoni @ 2017-11-05 8:55 UTC (permalink / raw) To: buildroot Hello, On Sun, 05 Nov 2017 08:43:05 +0100, Peter Korsgaard wrote: > > However, I agree that doing the DEVELOPERS change in a patch just > > modifying the package is perhaps not desirable. When adding a new > > package, yes, definitely, the DEVELOPERS entry should be added as part > > of the same patch. However, when a package is being modified, that's a > > different story, and the package change should be in a separate patch > > than the DEVELOPERS addition. > > I'm not sure it really matters much. A package change with a > modification of DEVELOPERS would most likely be for a version bump of an > unmaintained package where the person bumping wants to take over > ownership, or similar. > > I don't think it is a problem to update DEVELOPERS together with the > package in such cases, but keeping it separately is also fine. Agreed. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process 2017-11-03 21:10 [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process Joseph Kogut 2017-11-04 18:53 ` Baruch Siach @ 2017-11-05 20:14 ` Peter Korsgaard 1 sibling, 0 replies; 8+ messages in thread From: Peter Korsgaard @ 2017-11-05 20:14 UTC (permalink / raw) To: buildroot >>>>> "Joseph" == Joseph Kogut <joseph.kogut@gmail.com> writes: > Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com> > --- > docs/manual/contribute.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) Committed, thanks. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-11-05 20:14 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-11-03 21:10 [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process Joseph Kogut 2017-11-04 18:53 ` Baruch Siach 2017-11-04 22:14 ` Thomas Petazzoni 2017-11-05 6:07 ` Baruch Siach 2017-11-05 8:55 ` Thomas Petazzoni 2017-11-05 7:43 ` Peter Korsgaard 2017-11-05 8:55 ` Thomas Petazzoni 2017-11-05 20:14 ` Peter Korsgaard
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.