wrote: Actually these two functions aren't exactly the same, since the default return value differs. In practice that doesn't make a difference at the moment, but logically it would be wrong to

[...] Sorry, I meant "next to kernel-sec". Ben. -- Ben Hutchings, Software Developer   Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street

Hello all, I’m planning to take the Renesas LAVA worker [1] offline tomorrow morning (Wednesday UK time) for a few hours. We’re having a re-arrangement in the rack. If this is going to

I sent a new patch that takes a different approach. The new patch will only check that the necessary remotes are there. I also prepared a new separate script, for new users to prepare the local

The example and implementation use a colon (:) to specify remote mappings, but the command's help use the equal sign (=). Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> ---

Probably a copy&paste error that never got checked because nobody is using the mapping functionality. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> ---

This patch introduces some checks for the local git repository containing the remotes configured in conf/remotes.yml These checks occur at the beginning of import_stable.py, report_affected.py and

Hello Ben, Please consider these patches for cip-kernel-sec: [cip-kernel-sec 1/3] remotes: check that remotes exist This patch adds checks on the local repository and also provides a separate

I thought about that but in the future you may want to add some code that is specific to one of them. If you want me to consolidate them, what name would you use? Thanks, Daniel

I'm not yet convinced this is a good idea. After this change, we would still be assuming that there is a kernel repository or working tree next to kernel-config. If we wanted to be really helpful we

[...] Applied, thanks. Ben. -- Ben Hutchings, Software Developer   Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street

Maybe it would make more sense to merge the two functions instead? Ben. -- Ben Hutchings, Software Developer   Codethink Ltd https://www.codethink.co.uk/ Dale

[...] Applied, thanks. Ben. -- Ben Hutchings, Software Developer   Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street

Hi Laurence, apologies for the delay, but please do finally find two configs from Siemens attached. Best regards, Wolfgang

OK, I sent a patch for README. I also sent a patch for what it looks a small copy&paste mistake. OK, I sent a patch to address that. However, you were explicitly skiping "torvalds". Do you want me to

Users are required to prepare a local git repository, by default "../kernel", however there is no check at the moment. Alternatively, we could also create a repository for them (mkdir ../kernel; git

Currently the user is required to create its own remotes by hand. This should not be necessary, because the information is already collected in conf/remotes.yml. For that reason, if we detect that any

Otherwise, the script will not find all the expected tags and fail with a message like: fatal: ambiguous argument 'v5.1..torvalds/master': unknown revision or path not in the working

This is probably a copy&paste mistake that had no effect because the contents of _get_configured_remotes and _get_configured_branches is the same. Signed-off-by: Daniel Sangorrin

The Readme indicated some remote names (torvalds, stable) but not all of them. Ask the user to check conf/remotes.yml instead. I also added information on how to override or extend the configuration