<div dir="ltr">Abhijit,<div><br></div><div>I'm not sure OpenWrt has formally listed rules but here's the normal etiquette on these topics from other projects:<br><br>* Squashing commits is preferred. It reduces the work on reviewers and it's more useful to other users in case they need to pull out a single feature or change for their use-case.</div><div><br></div><div>* Sign-offs are usually only required when they leave an organization to the upstream project. In your case, if you're the submitter you should do the signoff which provides an assurance that you either wrote the code or know that other people wrote the code or included code which can be legally included. As an alternative, you could put a signoff line for each person who contributed (since they did already sign off on their work) but that's usually not done because of how long it could make the commits. If it's two sign-off lines, I doubt anyone is going to be annoyed but if it's 20, people may ask you to resubmit.</div><div><br></div><div>I hope that helps. If not, just let me know and I can try to help you out.</div><div><br></div><div>Thanks,</div><div><br></div><div>Eric</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 1:17 PM, Abhijit Mahajani <span dir="ltr"><<a href="mailto:Abhijit.Mahajani@imgtec.com" target="_blank">Abhijit.Mahajani@imgtec.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>

<div style="padding-bottom:40px">
<div style="font-size:10pt">
<p dir="ltr" style="margin-top:0;margin-bottom:0"> Copying in prpl mailing list.</p>
<p dir="ltr" style="margin-top:0;margin-bottom:0">Any advice much appreciated.</p><span class="">
<p dir="ltr" style="margin-top:0;margin-bottom:0"><br>
</p>
<p dir="ltr" style="margin-top:0;margin-bottom:0">Thanks and Regards,</p>
<p dir="ltr" style="margin-top:0;margin-bottom:0">Abhijit A. Mahajani</p>
</span></div>
<div style="font-size:10pt">
<p dir="auto" style="margin-top:0;margin-bottom:0"><br>
</p>
<p dir="auto" style="margin-top:0;margin-bottom:0">------ Original message------</p>
<p dir="auto" style="margin-top:0;margin-bottom:0"><b>From: </b>Abhijit Mahajani
</p>
<p dir="auto" style="margin-top:0;margin-bottom:0"><b>Date: </b>Wed, 14 Sep 2016 20:22</p>
<p dir="auto" style="margin-top:0;margin-bottom:0"><b>To: </b><a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.<wbr>org</a>;</p>
<p dir="auto" style="margin-top:0;margin-bottom:0"><b>Subject:</b>Re: [OpenWrt] Upstreaming related doubt
</p>
<p dir="auto" style="margin-top:0;margin-bottom:0"><br>
</p>
</div>
</div><div><div class="h5">
<font size="2"><span style="font-size:10pt">
<div>Hello,<br>
<br>
Another doubt related to upstreaming.<br>
<br>
When we submit a Pull request for Creator Ci40 i.e. pistachio soc support, do I need to maintain the commit history of all the changes done in our working repo or I can squash all the commits into 3-4 logical commits and send a Pull Request?<br>
<br>
Only problem is by squashing the commits I am losing original author/committer information., though I am adding Signed-Off-By fields to give the credit to those (and at the same time, people might not be interested in all the 100s of commits in the working
 repo, rather they would need only the "final" changes need to run Ci40) , so I am inclined towards squashing the commits, but if there is any policy on no. of commits or need to maintain the commit history in a Pull request then I am interested to know that.<br>
<br>
Kindly advice.<br>
<br>
<br>
Thanks and Regards,<br>
Abhijit A. Mahajani<br>
<br>
-----Original Message-----<br>
From: openwrt-devel [<a href="mailto:openwrt-devel-bounces@lists.openwrt.org" target="_blank">mailto:openwrt-devel-bounces@<wbr>lists.openwrt.org</a>] On Behalf Of <a href="mailto:openwrt-devel-request@lists.openwrt.org" target="_blank">openwrt-devel-request@lists.<wbr>openwrt.org</a><br>
Sent: Saturday, August 6, 2016 2:56 AM<br>
To: <a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.<wbr>org</a><br>
Subject: openwrt-devel Digest, Vol 128, Issue 5<br>
<br>
Send openwrt-devel mailing list submissions to<br>
        <a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.<wbr>org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
        <a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" target="_blank">
https://lists.openwrt.org/cgi-<wbr>bin/mailman/listinfo/openwrt-<wbr>devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
        <a href="mailto:openwrt-devel-request@lists.openwrt.org" target="_blank">openwrt-devel-request@lists.<wbr>openwrt.org</a><br>
<br>
You can reach the person managing the list at<br>
        <a href="mailto:openwrt-devel-owner@lists.openwrt.org" target="_blank">openwrt-devel-owner@lists.<wbr>openwrt.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific than "Re: Contents of openwrt-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
   1. Re: [OpenWrt] Upstreaming related doubt (Felix Fietkau)<br>
   2. Re: [LEDE-DEV] latency on PPPoA ADSL Annex A on using Lantiq<br>
      (Kevin Darbyshire-Bryant)<br>
   3. [PATCH] regmap: Fix debugfs for write-only devices (Cody Harris)<br>
   4. $5 OpenWRT Device on Kickstarter (Boken Lin)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Fri, 5 Aug 2016 12:01:55 +0200<br>
From: Felix Fietkau <<a href="mailto:nbd@nbd.name" target="_blank">nbd@nbd.name</a>><br>
To: Abhijit Mahajani <<a href="mailto:Abhijit.Mahajani@imgtec.com" target="_blank">Abhijit.Mahajani@imgtec.com</a>>,<br>
        "<a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.<wbr>org</a>" <<a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.<wbr>org</a>>,<br>
        "<a href="mailto:openwrt@lists.prplfoundation.org" target="_blank">openwrt@lists.prplfoundation.<wbr>org</a>" <<a href="mailto:openwrt@lists.prplfoundation.org" target="_blank">openwrt@lists.prplfoundation.<wbr>org</a>><br>
Subject: Re: [OpenWrt-Devel] [OpenWrt] Upstreaming related doubt<br>
Message-ID: <<a href="mailto:2a8dc348-407f-6297-1602-945293731859@nbd.name" target="_blank">2a8dc348-407f-6297-1602-<wbr>945293731859@nbd.name</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On 2016-08-05 11:41, Abhijit Mahajani wrote:<br>
> Hello All,<br>
> <br>
>  <br>
> <br>
> We have added Creator Ci40 into OpenWrt and its available at <br>
> <a href="https://github.com/CreatorDev/openwrt" target="_blank">https://github.com/CreatorDev/<wbr>openwrt</a>. We want to upstream our port to
<br>
> the openwrt community. However currently we have based on 4.1 kernel..<br>
> <br>
> I understand OpenWrt is with 4.4.14 right now, so If I want to create <br>
> a pull request for upstreaming Ci40 port, then do I need to first move <br>
> to<br>
> 4.4 or pull request with 4.1 is also fine?<br>
Please move to 4.4 first.<br>
<br>
- Felix<br>
<br>
<br>
------------------------------<br>
<br>
</div>
</span></font>
</div></div></div>

<br>______________________________<wbr>_________________<br>
OpenWrt mailing list<br>
<a href="mailto:OpenWrt@lists.prplfoundation.org">OpenWrt@lists.prplfoundation.<wbr>org</a><br>
<a href="http://lists.prplfoundation.org/cgi-bin/mailman/listinfo/openwrt" rel="noreferrer" target="_blank">http://lists.prplfoundation.<wbr>org/cgi-bin/mailman/listinfo/<wbr>openwrt</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px">Eric Schultz, Community Manager, prpl Foundation</span><br></div><div><a href="http://www.prplfoundation.org" target="_blank">http://www.prplfoundation.org</a></div><div><a href="mailto:eschultz@prplfoundation.org" target="_blank">eschultz@prplfoundation.org</a></div><div>cell: 920-539-0404</div></div></div></div></div></div></div>
</div>