threads / discuss / 54748

[Outreachy] Blog Post Submission

Subject: [Outreachy] Blog Post Submission

## tl;dr

5 messages between Dec 3, 2020 and Jan 26, 2021.

replies: 4people: 2as markdown or json

Sangeeta· Dec 3, 2020, 06:29 UTC · lore
Hey everyone!

I am very excited for working with Git this winter through outreachy. I have made a blogsite that would include the progress made after every 2 weeks(or maybe after every week).

I have added an introductory blog post regarding my journey to becoming an outreachy intern. Do give it a read.

https://sangu09.github.io/

Thanks and regards, Sangeeta

Sangeeta· Jan 26, 2021, 07:31 UTC · re: Sangeeta · lore

Re: [Outreachy] Blog Post Submission

Hey Everyone,

Here's my next blog post on the last few weeks update: https://sangu09.github.io/testcases/

Do read it and let me know if you have any suggestions.

Thanks and Regards, Sangeeta

Sangeeta· Dec 18, 2020, 10:12 UTC · lore

Re: [Outreachy] Blog Post Submission

Hey everyone,

Here's my second blog post on "everybody struggles". https://sangu09.github.io/everybody-struggles/

Do give it a read let me know if you have any suggestions.

Thanks and Regards, Sangeeta

On Fri, Dec 4, 2020 at 2:08 PM Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:

Show 55 quoted lines
>
> Hi Sangeeta,
>
> On 03/12/20 4:27 pm, Sangeeta wrote:
> >
> > First of all thanks for the feedback! I have made the changes.
> >
> > Secondly, regarding the microproject, it is still under review and I
> > read that in the mail[1](What's cooking in Git)(you can search for
> > "untracked" in the mail), Junio states that it is left on some changes
> > which I have already made in patch 7[2]. What is stopping me to reply
> > to that mail is that I might not have answers to some of the questions
> > that Danh asked[3](Should this change applicable to diff-index,
> > diff-files and other plumbing commands?) because I don't know whether
> > that would be breaking changes or not. I tried to test it in my local
> > and I found everything was working fine as expected but I don't know
> > the reason for that nor do I know the reason for whether things should
> > break or not. >
>
> Thanks for checking. Don't hesitate to reply to Danh's e-mail with what
> you've done and what you're not certain about. It's a good way to move
> things forward. Also, you could try Cc-ing people who seem to have
> worked in the diff code recently. For instance using `git log` to see
> the people who've modified the diff.c and `wt-status.c` recently, I
> could observe that:
>
>      Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
>
>      Elijah Newren <newren@gmail.com>
>
>      Jeff King <peff@peff.net>
>
> are some contributes who might be able to provide you some inputs.
>
> > [1] https://lore.kernel.org/git/xmqqtut6qf7q.fsf@gitster.c.googlers.com/
> > [2] https://lore.kernel.org/git/20201110083900.88161-1-sangunb09@gmail.com/
> > [3] https://lore.kernel.org/git/X6rJWpuUHz1qHYZL@danh.dev/
> >
> > To give you a context of my changes, I have made
> > `--ignore-submodules=untracked` the default for `git diff` when there
> > is no configuration variable or command-line option, to ensure that
> > the command doesn't give '-dirty' suffix to a submodule whose working
> > tree has untracked files. This was done to make it consistent with
> > `git describe`. For this, I had to make a global variable to check
> > whether ignoreSubmodules is set or not in the user config so that it
> > doesn't override that. Also to ensure that `git status` remains the
> > same, I have made `--ignore-submodules=none` the default for `git
> > status` so that the user doesn't end up deleting a submodule that has
> > uncommitted (untracked) files.
> >
>
> Also, thanks for the helpful summary!
>
> --
> Sivaraam
Felipe Contreras· Dec 18, 2020, 11:41 UTC · re: Sangeeta · lore

Re: [Outreachy] Blog Post Submission

Hello Sangeeta,
Sangeeta wrote:
> Here's my second blog post on "everybody struggles".
> https://sangu09.github.io/everybody-struggles/
> 
> Do give it a read let me know if you have any suggestions.
Just a few obsevations.
 1. Don't feel bad about the lack of code. In my professional experience
    I've seen situations where a developer spent one month working on a
    problem, and the solution is *one line* of code. It's not the amount
    of code that matters; it's the amount of effort that was put into
    it, and in fact; once you have a solution that works, putting more
    work can make it cleaner (less code), which is appreciated.
 2. There is a concept called "the curse of knowledge" [1] that everybody
    who is an expert in an area suffers. Certainly many old-timers in
    Git development do.
    That's why newcomers are always appreciated; fresh eyes usually spot
    issues many of us don't. You have a unique vantage point, so it's
    good that you document your struggles; they may give us an insight
    that otherwise we would be blind of.
 3. Once you have some code you would like to bounce off on Git
    developers, you might want to try git-related [2] (that's my tool
    but there are others). For example, I just did this:
    git related master..mergetool
    To find people to CC regarding the branch I'm currently working on
    (they have worked on the lines of code I'm changing).
That's it, I hope you find that useful.
Cheers.

[1] https://en.wikipedia.org/wiki/Curse_of_knowledge [2] https://github.com/felipec/git-related

-- 
Felipe Contreras
Sangeeta· Jan 8, 2021, 16:54 UTC · re: Felipe Contreras · lore

Re: [Outreachy] Blog Post Submission

Hey everyone,

Thanks for the much-needed motivation Felipe and also thanks for the tool. It would surely help me.

Meanwhile, I have come up with another blog post explaining my project here: https://sangu09.github.io/explaining-project/

Do give it a read and let me know what you think.

Thanks and Regards, Sangeeta

← back to recent threads