git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Shourya Shukla <periperidip@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog - Week 5
Date: Sun, 20 Jun 2021 07:52:18 +0200	[thread overview]
Message-ID: <CAP8UFD2sXjRgn6FqOcBor=Q_PXmy+xL4mHmV7Qy_fSrc0q+O9w@mail.gmail.com> (raw)
In-Reply-To: <D32894F5-FC76-4DD2-A2F6-E69AAE88C645@gmail.com>

On Sat, Jun 19, 2021 at 3:32 PM Atharva Raykar <raykar.ath@gmail.com> wrote:
>
> Here's the latest instalment of my weekly Git blog:
> http://atharvaraykar.me/gitnotes/week5

Great!

Just a note about:

> if (ps_matched[0]) {
>      if (!force)
>          die(_("'%s' already exists in the index"), path);
>      else if (!S_ISGITLINK(active_cache[i]->ce_mode))

The "else" above is not needed.

>          die(_("'%s' already exists in the index "
>              "and is not a submodule"), path);
>      break;
> }



> A peek at what's inside:
>
>  * The blog starts with a summary of all the relevant things
>    that have happened so far in my time with Git, including
>    the status of my submodule-related work.
>
>  * A question I had about reading the index into memory
>    (any kind of help would be appreciated!):
>    http://atharvaraykar.me/gitnotes/week5#some-challenges-with-the-changes-that-are-cooking
>
>  * Reflections, mostly as a note to myself and to people who
>    might be in a similar position as me in the future.
>
> Have a great weekend :)
>
> ---
> Atharva Raykar
> ಅಥರ್ವ ರಾಯ್ಕರ್
> अथर्व रायकर
>

  reply	other threads:[~2021-06-20  5:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 13:32 [GSoC] My Git Dev Blog - Week 5 Atharva Raykar
2021-06-20  5:52 ` Christian Couder [this message]
2021-06-21  6:20   ` Atharva Raykar
2021-06-20 19:16 ` Kaartic Sivaraam
2021-06-21  6:28   ` Atharva Raykar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8UFD2sXjRgn6FqOcBor=Q_PXmy+xL4mHmV7Qy_fSrc0q+O9w@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=periperidip@gmail.com \
    --cc=raykar.ath@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).