git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Usman Akinyemi <usmanakinyemi202@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, gitster@pobox.com,
	Patrick Steinhardt <ps@pks.im>,
	 phillip.wood123@gmail.com,
	Christian Couder <christian.couder@gmail.com>,
	 Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [RFC Outreachy] Leftoverbits, which involve replacing atoi with strtol or strtol_i or equivalent.
Date: Sun, 13 Oct 2024 03:46:05 +0000	[thread overview]
Message-ID: <CAPSxiM_U5ffBCsTrbBqsJK0jUZtAuWSLook8CLKat46CX0QC7g@mail.gmail.com> (raw)
In-Reply-To: <ZwqcHDzaR2U2JNu0@nand.local>

On Sat, Oct 12, 2024 at 3:56 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> Hi Usman,
>
> On Sat, Oct 12, 2024 at 11:21:13AM +0000, Usman Akinyemi wrote:
> > Hello,
> >
> > I was looking at some #leftoverbits which I can work on and I came
> > across this conversation.
> > https://public-inbox.org/git/CAC4O8c-nuOTS=a0sVp1603KaM2bZjs+yNZzdAaa5CGTNGFE7hQ@mail.gmail.com/
> >
> > I followed the conversation and came accross
> > three instances where I think atoi can be
> > converted to strtol or strtol_i or parse_timestamp().
> > These are the three files which I think the atoi can be
> > replaced with.
>
> This seems like a good #leftoverbits to use as an Outreachy
> contribution. From a brief skim, it looks like this is going in the
> right direction.
>
> But to get help from the rest of the list, please submit this change as
> a patch or patch series, following the instructions in:
>
>   - Documentation/MyFirstContribution.txt, and
>   - Documentation/SubmittingPatches
>
Thanks Taylor, I already went through these as I already sent my first
patch before.  Also, I already sent a patch as you suggested. Thank
you very much.
Usman Akinyemi.
> Thanks,
> Taylor

  reply	other threads:[~2024-10-13  3:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12 11:21 [RFC Outreachy] Leftoverbits, which involve replacing atoi with strtol or strtol_i or equivalent Usman Akinyemi
2024-10-12 15:56 ` Taylor Blau
2024-10-13  3:46   ` Usman Akinyemi [this message]
2024-10-15  0:42     ` Taylor Blau
2024-10-15  3:49       ` Usman Akinyemi
2024-10-15  3:54         ` Usman Akinyemi
2024-10-15  4:04           ` Usman Akinyemi
2024-10-16  1:25             ` Usman Akinyemi

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=CAPSxiM_U5ffBCsTrbBqsJK0jUZtAuWSLook8CLKat46CX0QC7g@mail.gmail.com \
    --to=usmanakinyemi202@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=phillip.wood123@gmail.com \
    --cc=ps@pks.im \
    --cc=sunshine@sunshineco.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).