All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Cc: git@vger.kernel.org,  nasamuffin@google.com
Subject: Re: [PATCH v4 0/3] Update MyFirstContribution.adoc to follow modern practices
Date: Mon, 19 May 2025 10:54:33 -0700	[thread overview]
Message-ID: <xmqq8qmso59i.fsf@gitster.g> (raw)
In-Reply-To: <20250518074317.73367-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Sun, 18 May 2025 13:13:14 +0530")

K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:

> The following changes are made to MyFirstContribution.adoc 
> to make the tutorial follow modern git practices.
>
> The tutorial codes actually help newbies like myself to actually know what is going on 
> in the source code as the Git source code is vast.
>
> Therefore these patches.
>
> K Jayatheerth (3):
>   docs: remove unused mentoring mailing list reference
>   docs: clarify cmd_psuh signature and explain UNUSED macro
>   docs: replace git_config to repo_config
>
>  Documentation/MyFirstContribution.adoc | 55 +++++++++++++++-----------
>  1 file changed, 33 insertions(+), 22 deletions(-)

Looking much better.  Will queue.

Thanks.

      parent reply	other threads:[~2025-05-19 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18  7:43 [PATCH v4 0/3] Update MyFirstContribution.adoc to follow modern practices K Jayatheerth
2025-05-18  7:43 ` [PATCH v4 1/3] docs: remove unused mentoring mailing list reference K Jayatheerth
2025-05-18  7:43 ` [PATCH v4 2/3] docs: clarify cmd_psuh signature and explain UNUSED macro K Jayatheerth
2025-05-19 17:55   ` Junio C Hamano
2025-05-18  7:43 ` [PATCH v4 3/3] docs: replace git_config to repo_config K Jayatheerth
2025-05-19 17:54 ` Junio C Hamano [this message]

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=xmqq8qmso59i.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jayatheerthkulkarni2005@gmail.com \
    --cc=nasamuffin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.