All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: karthik nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2024, #11; Fri, 25)
Date: Sun, 27 Oct 2024 19:52:52 -0400	[thread overview]
Message-ID: <Zx7SVFV1aUmU/zBy@nand.local> (raw)
In-Reply-To: <CAOLa=ZS3gqv6bB+gLxeYUmu70hJm3=8paJFWU5OLpG1dG9Zr5g@mail.gmail.com>

On Sun, Oct 27, 2024 at 02:26:08PM -0700, karthik nayak wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> Hello,
>
> [snip]
>
> > * kn/arbitrary-suffixes (2024-10-24) 1 commit
> >  - CodingGuidelines: discourage arbitrary suffixes in function names
> >
> >  Update the project's CodingGuidelines to discourage naming functions
> >  with a "_1()" suffix.
> >
> >  Will merge to 'next'?
> >  source: <20241024105357.2605168-1-karthik.188@gmail.com>
> >
>
> I think we can probably merge this down. We can always iterate on it if
> needed.
>
> [snip]
>
> > * kn/ci-clang-format-tidy (2024-10-18) 2 commits
> >  - clang-format: align consecutive macro definitions
> >  - clang-format: re-adjust line break penalties
> >
> >  Updates the '.clang-format' to match project conventions.
> >
> >  Will merge to 'next'?
> >  source: <cover.1729241030.git.karthik.188@gmail.com>
> >
>
> Justin did leave a review, so we could probably merge this too.

Great, let's start merging both of these down. Thanks for the update.


Thanks,
Taylor

  reply	other threads:[~2024-10-27 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 19:40 What's cooking in git.git (Oct 2024, #11; Fri, 25) Taylor Blau
2024-10-27 21:26 ` karthik nayak
2024-10-27 23:52   ` Taylor Blau [this message]
2024-10-28  5:43 ` Patrick Steinhardt
2024-10-28 17:37   ` Taylor Blau

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=Zx7SVFV1aUmU/zBy@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@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.