<oriansj>Guest_30: well the answer to that is rather simple ask questions about what needs to be done. We have documentation that needs writing, tests to create, code to clean up and lots of pieces that are available for all levels of technical skill (even art work if you are so inclined) <fossy>I will implement cd now that I am not sick <oriansj>zig: well we don't know if they are just going to read the log for our answer or which to engage in their personal nick rather than just guest. So disappearing doesn't mean much <oriansj>fossy: that is great to hear; I'll check that out (and merge) shortly <oriansj>The only thing I see which could be done better is envp_length could just be a global and you wouldn't have to calloc it <oriansj>I look forward to your cd implementation ^_^ <oriansj>It'll be nice for mescc-tools to finally have a more resonable shell environment to work with <oriansj>dddddd: one little trick for git: git filter-branch --prune-empty -d /dev/shm/scratch --index-filter "git rm --cached -f --ignore-unmatch FileTo.Remove" --tag-name-filter cat -- --all <oriansj>just remember to replace FileTo.Remove with the actual file to pull (debconf_2019/package-lock.json in this case) <oriansj>dddddd: and those commits were pulled; it was a git rebase, so yeah.... <fossy>oriansj: or bfg repo cleaner <dddddd>Thanks oriansj. More commits than required were touched but looks fine now. ***ng0_ is now known as ng0
<lfam>Alright rain1, how are you? ***janneke_ is now known as janneke