On 11/1/24 6:42 PM, Sergey Bugaev wrote:
I'm only seeing a single "patch", namely this cover letter. Did you
perhaps accidentally run your git send-email on a single patch file
instead of on the whole series?
This is the issue of the mail service provider I'm using. I will try to
switch to anoth
On Fri, Nov 1, 2024 at 1:46 PM Zhaoming Luo wrote:
> Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): y
> 250 OK
> ...propagated at /usr/lib/git-core/git-send-email line 1696,
> line 2.
Hm, I have no idea about this kind of thing. git-send-email line 1696
in my copy of Git v2.47.0 is just
On 11/1/24 6:42 PM, Sergey Bugaev wrote:
I'm only seeing a single "patch", namely this cover letter. Did you
perhaps accidentally run your git send-email on a single patch file
instead of on the whole series?
When I use `git send-email *.patch`, 0/3 patch can be sent perfectly, but
when I type '
On Fri, Nov 1, 2024 at 1:30 PM Zhaoming Luo wrote:
> I think it's a good chance to stop
> and gather some suggestions and feedback, so I sent a series of RTC patches.
Hi Zhaoming,
I'm only seeing a single "patch", namely this cover letter. Did you
perhaps accidentally run your git send-email on
Hello,
Zhaoming Luo, le ven. 01 nov. 2024 18:28:04 +0800, a ecrit:
> Currently I am working on adding /dev/rtc. For now I can compile it and
> use `settrans` to create a device file; I can confirm that ioctl() works
> perfectly on the generated device file.
Congrats :)
> The next thing I'm going
