You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Xiang Xiao <xi...@gmail.com> on 2019/12/17 16:09:50 UTC
patch for ntpclient: merge xmit and recv buffer into one to save the stack
another patch fix warning: 'g_nullstring' defined but not used.
Thanks
Xiang
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Dec 17, 2019 at 11:40 AM Xiang Xiao <xi...@gmail.com> wrote:
> It seems that I can't attach the file to dev@nuttx.apache.org:(.
> My attachment in previous email also lose:
> https://lists.apache.org/thread.html/9bc6f92e39b9d2f401e1554c0e3270d574067ff608d13df1c1c1b11e%40<dev.nuttx.apache.org>
>
> Justin, can we send the attachment to dev@nuttx.apache.org?
>
> On Wed, Dec 18, 2019 at 12:17 AM Gregory Nutt <sp...@gmail.com> wrote:
> >
> >
> > > another patch fix warning: 'g_nullstring' defined but not used.
> > I don't see anything attached.
Copying Justin on this...
It's a pretty major problem if we can't use attachments here because
much of the NuttX community contributes by patches.
Thanks,
Nathan
RE: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by David Sidrane <Da...@nscdg.com>.
+1
-----Original Message-----
From: Gregory Nutt [mailto:spudaneco@gmail.com]
Sent: Tuesday, December 17, 2019 8:07 PM
To: dev@nuttx.apache.org
Subject: Re: patch for ntpclient: merge xmit and recv buffer into one to
save the stack
> Should we enable the attachment before the new workflow settle? so the
> traditional workflow can transfer from google group to here
> immediately.
There is no reason to send patches to any of the Apache resources now.
They cannot be used there until the repositories are in place and we
have at least a functional description of the workflow. All patches
will be applied to the Bitbucket repositories until that two things are
in place. I suggest that you continue to send patch to the Google group
until then.
Greg
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Gregory Nutt <sp...@gmail.com>.
> Should we enable the attachment before the new workflow settle? so the
> traditional workflow can transfer from google group to here
> immediately.
There is no reason to send patches to any of the Apache resources now.
They cannot be used there until the repositories are in place and we
have at least a functional description of the workflow. All patches
will be applied to the Bitbucket repositories until that two things are
in place. I suggest that you continue to send patch to the Google group
until then.
Greg
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Xiang Xiao <xi...@gmail.com>.
Should we enable the attachment before the new workflow settle? so the
traditional workflow can transfer from google group to here
immediately.
Thanks
Xiang
On Wed, Dec 18, 2019 at 5:55 AM Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> Other project use in no particular order:
> - GitHub issues
> - JIRA
> - Mailing list
> - Github PRs
>
> Some (most?) accept multiple ways of submitting patches.
>
> Thanks,
> Justin
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Other project use in no particular order:
- GitHub issues
- JIRA
- Mailing list
- Github PRs
Some (most?) accept multiple ways of submitting patches.
Thanks,
Justin
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Gregory Nutt <sp...@gmail.com>.
>
>>> Justin, can we send the attachment to dev@nuttx.apache.org?
>> You can but it increases the chance the email will be marked as spam.
>> I believe we can ask Infra to modify that.
>
> How do other projects accept patches? If there is a more standard
> way, we should consider that.
I find a lot of good information on the Apache Commons project pages:
*Submitting A Patch. * Please use JIRA, patches sent to the mailing
lists are harder to track and use up more bandwidth.
https://commons.apache.org/patches.html
We don't have have Jira set up, do we? Should continue to take patches
on the Google group until Jira is available.
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Gregory Nutt <sp...@gmail.com>.
>> Justin, can we send the attachment to dev@nuttx.apache.org?
> You can but it increases the chance the email will be marked as spam. I believe we can ask Infra to modify that.
How do other projects accept patches? If there is a more standard way,
we should consider that.
Greg
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Justin, can we send the attachment to dev@nuttx.apache.org?
You can but it increases the chance the email will be marked as spam. I believe we can ask Infra to modify that.
Thanks,
Justin
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Xiang Xiao <xi...@gmail.com>.
It seems that I can't attach the file to dev@nuttx.apache.org:(.
My attachment in previous email also lose:
https://lists.apache.org/thread.html/9bc6f92e39b9d2f401e1554c0e3270d574067ff608d13df1c1c1b11e%40<dev.nuttx.apache.org>
Justin, can we send the attachment to dev@nuttx.apache.org?
On Wed, Dec 18, 2019 at 12:17 AM Gregory Nutt <sp...@gmail.com> wrote:
>
>
> > another patch fix warning: 'g_nullstring' defined but not used.
> I don't see anything attached.
Re: patch for ntpclient: merge xmit and recv buffer into one to save
the stack
Posted by Gregory Nutt <sp...@gmail.com>.
> another patch fix warning: 'g_nullstring' defined but not used.
I don't see anything attached.