git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Dealing with corporate email recycling

From
Philip Oakley <philipoakley@iee.email>
Date
Mar 15, 2022, 11:15 UTC
Message-ID
<eecab055-94bc-2174-0490-28b76cf48b0e@iee.email>
In-Reply-To
<87y21c2ehl.fsf@gmail.com>
On 15/03/2022 01:23, Sean Allred wrote:
Show 14 quoted lines
> Philip Oakley <philipoakley@iee.email> writes:
>> A broader issue for the corporate email mailbox systems is those that
>> are allocated to roles. So you may have Traning1@corp.com thru
>> Training9@corp.com (we had) and if that training includes practical low
>> hanging fruit examples from a project, it's difficult to disambiguate
>> those commits. More likely is say, having TestPC1 - TestPC9 that
>> included debug commits, perhaps even with pair programming test & debug
>> sessions, so allocation to individuals (rather than mailbox) becomes a
>> real problem. Hopefully that's rare in Sean's case.
> Yep, this wouldn't happen for us.  Lots of other processes depend on
> there being an individual making the commit.
>
> I'd also be surprised if this didn't cause process problems for other
> folks, too.

I was in equipment engineering where independent dedicated test equipment was more common, rather than pure software, so the potential for  role based commits from TestPC1 - TestPC9 was far more likely (for cases where it's the hardware that needs to be understood, not the engineers' choice of code ;-)

Previous: Sean AllredNext: Philip Oakley
Message 18 of 28 in “Dealing with corporate email recycling”
  1. Sean AllredMar 12, 2022
  2. Junio C HamanoMar 13, 2022
  3. rsbecker@nexbridge.comMar 13, 2022
  4. Sean AllredMar 13, 2022
  5. rsbecker@nexbridge.comMar 13, 2022
  6. Sean AllredMar 13, 2022
  7. rsbecker@nexbridge.comMar 13, 2022
  8. Sean AllredMar 13, 2022
  9. Philip OakleyMar 13, 2022
  10. Sean AllredMar 13, 2022
  11. Junio C HamanoMar 13, 2022
  12. rsbecker@nexbridge.comMar 13, 2022
  13. Junio C HamanoMar 14, 2022
  14. Philip OakleyMar 14, 2022
  15. Junio C HamanoMar 14, 2022
  16. Philip OakleyMar 14, 2022
  17. Sean AllredMar 15, 2022
  18. Philip OakleyMar 15, 2022
  19. Philip OakleyMar 13, 2022
  20. Sean AllredMar 13, 2022
  21. Philip OakleyMar 14, 2022
  22. Ævar Arnfjörð BjarmasonMar 13, 2022
  23. brian m. carlsonMar 13, 2022
  24. rsbecker@nexbridge.comMar 13, 2022
  25. rsbecker@nexbridge.comMar 13, 2022
  26. Sean AllredMar 13, 2022
  27. Sean AllredMar 15, 2022
  28. Peter KreftingMar 18, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.