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

Re: Collaborative community interview for Git's 20th anniversary

From
Luca Milanesio <luca.milanesio@gmail.com>
Date
Apr 14, 2025, 12:37 UTC
Message-ID
<04A328E9-1146-4D4A-84E7-456FFEB66A5A@gmail.com>
In-Reply-To
<85ea4aa0-c595-4f0b-a2ac-d0113aca464a@gmail.com>
Show 10 quoted lines
> On 14 Apr 2025, at 13:31, Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
> 
> Hello all,
> 
> As part of the Git's 20th year anniversary, we from the Git Rev News team are thinking of doing a community interview where we would share a list of questions that we've prepared and we would like to welcome answers from anyone in the community for them. We could gather the answers for them upto a particular time (like 25/April or so) and begin curating the answers into a special interview for this month's edition. The questions are below. Feel free to respond with your answers to this mail thread. Let me know if I've missed to include any particularly compelling question.
> 
>  - What's your favorite Git trick or workflow that you wish more people
>    knew about?
> 
>  - What was your worst Git disaster, and how did you recover from it?

I suspect to be one of the worst offenders :-) https://www.infoq.com/news/2013/11/use-the-force/

Thankfully I was using Gerrit Code Review and the replication plugin: the refs were not lost but just rewind and we could reset all the correct SHA1s for all of them.
> 
>  - If you could go back in time and change one design decision in Git,
>    what would it be?
Use SHA-256 straight away, as it was published 24 years ago and already existed at the time Git was designed.
Luca.
Show 26 quoted lines
> 
>  - Which Git feature or improvement over the past 20 years do you think
>    had the biggest impact on your workflow?
> 
>  - What Git problem that existed 10 years ago has been most
>    successfully solved?
> 
>  - Which Git commands or workflows do you think are still misunderstood
>    or underutilized today?
> 
>  - What's one Git based project, tool, or extension you think deserves
>    more recognition from the community?
> 
>  - What Git feature or capability surprised you most when you first
>    discovered it?
> 
>  - What's your boldest prediction about how version control might look
>    in another 20 years?
> 
> 
> Looking forward to see interesting answers. :-)
> 
> --
> Sivaraam for the Git Rev News team.
> 
> 
Previous: Kaartic SivaraamNext: Lucas Seiki Oshiro
Message 2 of 6 in “Collaborative community interview for Git's 20th anniversary”
  1. Kaartic SivaraamApr 14, 2025
  2. Luca MilanesioApr 14, 2025
  3. Lucas Seiki OshiroApr 14, 2025
  4. Elijah NewrenApr 23, 2025
  5. Kaartic SivaraamMay 2, 2025
  6. Kaartic SivaraamMay 2, 2025

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.