11097 2017-02-23 05:19:23 +0000 Create persistent dummy git user 2026-06-25 15:20:46 +0000 1 1 6 Yocto Project Subprojects CROPS crops-default 3.1 x86 Multiple NEW Medium enhancement Future 11385 1 juro.bystricky unassigned amber.n.elliot randy.e.witt randy.macleod richard.purdie sgw tim.orling --- --- Don't know oldest_to_newest 70888 0 juro.bystricky 2017-02-23 05:19:23 +0000 When building bitbake images in containers one cannot do $ git stash without always being prompted to set git user name and user email. The values, once entered, are not persistent in the container so this gets very annoying after a short while. One solution would be to create some persistent dummy git settings for user "Johny Container" or something like that. 78622 1 brian.avery 2017-12-08 22:05:33 +0000 Moving to Joshua. Making a dummy git user is not the best way to solve this. Either: 1) run git commands in the workdir from the host side where you gitconfig is in ~/.gitconfig -or- 2) run docker as : docker run -it --env GIT_CONFIG=/myCONFIG -v ~/.gitconfig:/myCONFIG:ro -v `pwd`:`pwd` crops/poky --workdir=`pwd` Which gives you: pokyuser@ff47ab906591:/home/bavery/src/myBugs$ git config --list user.email=brian.avery@intel.com user.name=brian avery ** inside the container ** .... This usage probably just needs to be documented then the big could be closed ... 97115 2 randy.macleod 2023-10-30 15:37:26 +0000 Build move to 5.0 -- ../Randy 98846 3 randy.macleod 2024-04-25 01:13:57 +0000 Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue. 98868 4 randy.macleod 2024-04-25 01:23:12 +0000 Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please. 106015 5 tim.orling 2026-06-25 15:20:46 +0000 Ideas here are probably still valid for future design considerations. Moving to future.