From: Atharva Raykar <raykar.ath@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>,
Shourya Shukla <periperidip@gmail.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog — Week 6
Date: Mon, 28 Jun 2021 13:05:44 +0530 [thread overview]
Message-ID: <6305ED7B-0C92-4C14-9F75-2EC3B24A6D2F@gmail.com> (raw)
In-Reply-To: <60d8aefdb7f1a_ba9f3208ca@natae.notmuch>
On 27-Jun-2021, at 22:31, Felipe Contreras <felipe.contreras@gmail.com> wrote:
>
> Atharva Raykar wrote:
>
>> * Reflections:
>> - How does Git even start?
>> (https://atharvaraykar.me/gitnotes/week6#how-does-git-even-start)
>> This was just something I was curious about, not really important
>> to my project. If anyone knows the answer to what I asked in that,
>> section, it would be nice to know!
>
> They are not all linked together.
>
> Take for example shell.c, which will be used to generate shell.o, which
> is used here:
>
> PROGRAM_OBJS += shell.o
>
> PROGRAM_OBJS is used here:
>
> PROGRAMS += $(patsubst %.o,git-%$X,$(PROGRAM_OBJS))
>
> This means shell.o will be used to generate a program called git-shell.
>
> But the "git" program will not use PROGRAM_OBJS, therefore it will not
> link shell.o.
Thanks, that explained a lot of things for me, and I noticed
'git.c:cmd_main()' does indeed call these separately created
executables (like git-shell).
I'll try to update my blog post with this explanation when I get
some free time for it.
next prev parent reply other threads:[~2021-06-28 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 11:24 [GSoC] My Git Dev Blog — Week 6 Atharva Raykar
2021-06-27 17:01 ` Felipe Contreras
2021-06-28 7:35 ` Atharva Raykar [this message]
2021-06-27 22:07 ` Christian Couder
2021-06-28 7:48 ` Atharva Raykar
[not found] ` <CACdWUYWOsU+oHDNnur_NCSBuMfea95rKqrS5z2x-JRc_C0iyfg@mail.gmail.com>
2021-06-28 17:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6305ED7B-0C92-4C14-9F75-2EC3B24A6D2F@gmail.com \
--to=raykar.ath@gmail.com \
--cc=christian.couder@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=periperidip@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.
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 NNTP newsgroup(s).