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,  ben.knoble@gmail.com
Subject: Re: [GSOC][PATCH v2] Remove outdated mentoring mailing list reference
Date: Fri, 21 Mar 2025 03:36:22 -0700	[thread overview]
Message-ID: <xmqqa59evffd.fsf@gitster.g> (raw)
In-Reply-To: <20250319170244.32912-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Wed, 19 Mar 2025 22:32:44 +0530")

K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:

> Subject: Re: [GSOC][PATCH v2] Remove outdated mentoring mailing list reference

[Documentation/SubmittingPatches]

    The first line of the commit message should be a short description (50
    characters is the soft limit, see DISCUSSION in linkgit:git-commit[1]),
    and should skip the full stop.  It is also conventional in most cases to
    prefix the first line with "area: " where the area is a filename or
    identifier for the general area of the code being modified, e.g.

    * doc: clarify distinction between sign-off and pgp-signing
    * githooks.txt: improve the intro section

    If in doubt which identifier to use, run `git log --no-merges` on the
    files you are modifying to see the current conventions.

> and clarify tutorial prerequisites

Do not do this.  What you have on the e-mail "Subject:" line is the
first paragraph (whose definition is block of text delineated by
blank lines) of the commit log message, and the first paratraph in
the body of a patch e-mail is the second paragraph.  You do not
start your second paragraph at half-sentence, as if it were a
continuation of an incomplete previous sentence.


  reply	other threads:[~2025-03-21 10:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 18:15 [GSOC][PATCH 1/3] Remove outdated mentoring mailing list reference and clarify tutorial prerequisites K Jayatheerth
2025-03-15 18:15 ` [GSOC][PATCH 2/3] Update function signature and UNUSED to include struct repository and modify builtin.h accordingly K Jayatheerth
2025-03-15 18:15 ` [GSOC][PATCH 3/3] Replace git_config(...) with repo_config(...) for modern Git compatibility K Jayatheerth
2025-03-15 18:21   ` JAYATHEERTH K
2025-03-17 21:57 ` [GSOC][PATCH 1/3] Remove outdated mentoring mailing list reference and clarify tutorial prerequisites Junio C Hamano
2025-03-19 17:02   ` [GSOC][PATCH v2] Remove outdated mentoring mailing list reference K Jayatheerth
2025-03-21 10:36     ` Junio C Hamano [this message]
2025-03-21 14:30       ` [[GSOC][PATCH v3] 1/3] docs: drop inactive mentoring list, add C prereq K Jayatheerth
2025-03-21 14:30         ` [[GSOC][PATCH v3] 2/3] docs: update function signature, add UNUSED macro K Jayatheerth
2025-03-23 22:08           ` Junio C Hamano
2025-03-21 14:30         ` [[GSOC][PATCH v3] 3/3] docs: replace git_config with repo_config K Jayatheerth
2025-03-23 22:08           ` Junio C Hamano
2025-03-24  1:42             ` JAYATHEERTH K
2025-03-24  4:46               ` Junio C Hamano
2025-03-24 13:03                 ` [[GSOC][PATCH v4] 2/3] docs: update function signature, add UNUSED macro K Jayatheerth
2025-03-24 13:03                   ` [[GSOC][PATCH v4] 3/3] docs: replace git_config with repo_config K Jayatheerth
2025-03-24 13:10                 ` [[GSOC][PATCH v3] " JAYATHEERTH K
2025-03-26  2:37                   ` Junio C Hamano
2025-03-26  3:15                     ` JAYATHEERTH K
2025-03-29 17:42                       ` JAYATHEERTH K
2025-03-21 14:32       ` [GSOC][PATCH v2] Remove outdated mentoring mailing list reference JAYATHEERTH K

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=xmqqa59evffd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jayatheerthkulkarni2005@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 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.