On 2023-01-09, Simon Tournier wrote:
> On ven., 06 janv. 2023 at 10:42, Vagrant Cascadian wrote:
>> More I wanted to look through the patch text rather than the package
>> descriptions. It would ideally catch things like "reproducible" or
>> "deterministic" in comments in patches as well as git co
Hi Vagrant,
On ven., 06 janv. 2023 at 10:42, Vagrant Cascadian wrote:
> More I wanted to look through the patch text rather than the package
> descriptions. It would ideally catch things like "reproducible" or
> "deterministic" in comments in patches as well as git commit summary.
Well, IIUC, y
On 2023-01-06, Simon Tournier wrote:
> On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian wrote:
>
>> Perhaps a description would for the team(s) would help a bit here. I
>> see embedded as dealing with bootloaders or firmware commonly used on
>> embedded systems, and perhaps cross-compilers?
>
> We
Hi Vagrant,
On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian wrote:
> Perhaps a description would for the team(s) would help a bit here. I
> see embedded as dealing with bootloaders or firmware commonly used on
> embedded systems, and perhaps cross-compilers?
Well, currently the ’team’ record c
I filed a couple patches related to teams recently, which pointed out a
few things about the teams process to me...
First off, I wonder if there is (or it is worth creating) a way to make
the scope of a team more fine-grained... e.g. I think the Embedded team
would want to be notified of changes
