public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: SoutrikDas <valusoutrik@gmail.com>
To: shreyanshpaliwalcmsmn@gmail.com
Cc: git@vger.kernel.org, valusoutrik@gmail.com
Subject: Re: [PATCH] doc: fix repo_config documentation reference
Date: Fri,  6 Feb 2026 11:31:56 +0530	[thread overview]
Message-ID: <20260206060156.73753-1-valusoutrik@gmail.com> (raw)
In-Reply-To: <20260205131132.44282-1-shreyanshpaliwalcmsmn@gmail.com>

- Documenation spelling corrected

> First describe the current problem statement which describes the 
> current state in the present tense like 
> "In MyFirstContribution.adoc, the link to the repo_config() 
> documentation is invalid because the documentation related was 
> moved to a different file."

Let this be A 

> Then you instruct somebody to make changes to the code to make it 
> better like 
> Replace the path for the repo_config() documentation from 
> 'Documentation/technical/api-config' to 'config.h'.

Let this be B

So the Commit will be 
> <short tile> 
> 
> <B> 

And the cover mail for that patch will be 
> <short tile same as commit message ? > 
> 
> <A>
>
> <B> 

I configured my git send-email because I couldnt reply to your email
with gitgitgadget ... maybe it was my mistake. Anyway I wanted to ask
Now that I have changed the commit message , what should I do ? 
Should I send a [PATCH v2] as a seperate thread or send it here ?


  reply	other threads:[~2026-02-06  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 12:03 [PATCH] doc: fix repo_config documentation reference Soutrik Das via GitGitGadget
2026-02-05 13:11 ` Shreyansh Paliwal
2026-02-06  6:01   ` SoutrikDas [this message]
2026-02-06  6:21     ` [GSOC PATCH v2] " SoutrikDas
2026-02-06 16:39       ` Junio C Hamano

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=20260206060156.73753-1-valusoutrik@gmail.com \
    --to=valusoutrik@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=shreyanshpaliwalcmsmn@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