ZheNing HuHello，Git!
### Self introduction
I'm ZheNing Hu, I am very lucky to participate in the GSoC git project this year. Many people in the git community already have given me a lot of help in the past few months. Junio, Christian, Peff, Eric, Denton..., it's great to get along with you guys! Your review and guidance have greatly benefited my growth.
In these days before GSoC, I learned some simple command implementation and data structures of git, learned strict coding standards and learned how to test, More importantly, I learned how to communicate with these kind-hearted reviewers.
Of course, there are still many difficulties for me: * My poor English sometimes can’t express the meaning clearly. * The Git architecture is very large, even a small command may require very complex logic to implement, I often feel very difficult to find clues.
Therefore, during GSoC, I hope to overcome these difficulties and learn more in-depth knowledge in git.
### How to complete my GSoC project
I don’t want to be rejected by Git after I have completed a lot of content, as Olga once did, Therefore, I think it is best to move in the right direction step by step under everyone's supervision.
Current condition: 1. In order to use a unified interface containing both short-named and full-named atoms, inspired by the short name option and long name option of "OPT_*" in `parse-options.h`, I thought I should add a new short name atom to `struct valid_atom` for expansion in `ref-filter.c`, In [1]: Junio thinks that `--format` with two-letters short atoms should not be implemented in `ref-filter.c` and provided for the `for-each-ref` family. Instead, let the "log" family learn the full-named atom. To ensure the consistency of `log --format` and `for-each-ref --format`. But for now, It seems that the parsing of full-named atoms in `pretty.c` is not very elegant. E.g.
if (skip_prefix(placeholder, "(describe", &arg)) {
...
} if (skip_prefix(placeholder, "(trailers", &arg)) {
...
}We should have an atom table like `valid_atom` in `ref-filter.c`, but this is missing in `pretty.c`. So how do we complete the unification of the two types of atoms now?
2. "50cfe1f([GSOC] ref-filter: introduce enum atom_type)" has been merged into the `next` branch, should we focus on the performance optimization of `ref-filter.c`? Finally, we can build a `format_cat_file_item()` similar to `format_ref_array_item()`, which should not be difficult. And we have to make sure that the performance of `cat-file --batch` is not lower than before.
### The connection between Git and the file system
I am currently studying operating system course, git as a file system on top of the file system. There are many differences and similarities with ordinary file systems. I am very curious about this knowledge, do not know if there are any relevant reading materials?
### Motto
I remember I saw an interview about Junio and Dan Kogai before [2]:
Dan: What do you think is a "good engineer"?
Junio: When I took over the maintainer of Git, Linus told me that star engineers have three qualities. The most important thing is to be able to keep doing one thing all the time. In that sense, you can't be an alpha geek. It's sharp and you can jump to a new one right away, but don't get bored right away.
In other words, it’s one thing to have enthusiasm, but it’s more important to persevere.
When I read the Git source code, I can see the code written by Peff 15 years ago and the code written by Peff a few months ago, which is very touching. It's as if you guys can travel through time and space.
So, I hope I can also persevere and fight for interest. After 15 years, let’s take a look at the code I wrote today :)
[1]:https://lore.kernel.org/git/xmqqk0nz72on.fsf@gitster.g/ [2]:https://gihyo.jp/dev/serial/01/alpha-geek/0040?page=2
