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

[GSoC] Intro and Micro-project

From
EFEdwin Fernando <edwinfernando734@gmail.com>
Date
Mar 21, 2023, 14:38 UTC
Message-ID
<CAPNJDgcauhz_NraSPTQfiDM61gyghSJShZLPUtt5HOr2xKysZg@mail.gmail.com>

Hello, I am Edwin, a first year undergrad in the department of computing, Imperial College London. This is my first message to this mailing list! I want to work on the micro-project "avoiding pipelines in test scripts". I'm really excited to work on such a massive project (ie, git, not the microproject) and be in contact with the people who put it all together. I'm curious about how software development works at this scale, since it feels quite different from the small projects I've used to work on. I use bash quite frequently for automating tasks, and I have experience in C, through a uni project of making an assembler.

I found and looked at a few places with pipes. I have a few thoughts and questions on making a change. Firstly (if this is relevant), how do I ensure that the file I write the std output to doesn't have a name clash with other such files made during tests?

I will follow up with an email of the proposed patch. Regards, Edwin.

Next: Felipe Contreras
Message 1 of 5 in “[GSoC] Intro and Micro-project”
  1. Edwin FernandoMar 21, 2023
  2. Felipe ContrerasMar 21, 2023
  3. Taylor BlauMar 21, 2023
  4. Junio C HamanoMar 21, 2023
  5. Taylor BlauMar 21, 2023

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.