smoltcp: use a fork instead of a local copy

未关闭
#744 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
git, github, rust

调研方向

The work is the vendored smoltcp copy inside the Awkernel repository and the Cargo dependency entries that point at it. First confirm with the maintainer (@ytakano, who is asked directly in the issue) that a tier4 fork is wanted, and identify which local changes are the Awkernel patches. Done means a tier4 smoltcp fork holds those patches in one commit, the local copy is removed, and Awkernel's Cargo manifests build against the fork.

由索引模型根据 Issue 内容生成。

描述

I noticed that the current smoltcp is a customized copy of the official smoltcp crate.

In order to make it easier to benefit from future improvements in smoltcp, I suggest the following actions:

  1. Make a fork of the original smoltcp in https://github.com/tier4
  2. Push a commit to this new fork with all the patches required for Awkernel
  3. Remove the copy of smoltcp from Awkernel
  4. Point to this fork in Awkernel dependency lists

The main advantage of this is that it is possible to sync the fork with the original repo, thus benefitting from potential future improvements and error fixes.

@ytakano what do you think?

主要语言
Rust
星标
282
派生
12
平均合并
2 天 9 小时
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tier4/awkernel 的其他 Issue

查看 tier4/awkernel 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。