From: Alison Schofield <alison.schofield@intel.com>
To: Saasha Gupta <saashaa1122@gmail.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: unable to submit patch with git send email
Date: Mon, 1 Apr 2024 12:29:04 -0700 [thread overview]
Message-ID: <ZgsLAL2sELdJ9/h2@aschofie-mobl2> (raw)
In-Reply-To: <CAN=P6FPOSOW6uKoYrmEB_7tHub8Ba09Vftjw0eeniL_MK01CPw@mail.gmail.com>
On Tue, Apr 02, 2024 at 12:56:06AM +0530, Saasha Gupta wrote:
> Dear Alison,
>
> Thanks for the advice. I do indeed have a format-patch available,
> which I tried sending via "mutt -H pkgname.patch"
>
> Mutt throwed error 70.
How did you send this email? Are you using mutt?
(please don't trim recipients in an in progress thread)
--Alison
>
> Saasha
>
> On Mon, Apr 1, 2024 at 11:15 PM Alison Schofield
> <alison.schofield@intel.com> wrote:
> >
> > On Mon, Apr 01, 2024 at 10:43:53PM +0530, Saasha Gupta wrote:
> > > Dear maintainers of the outreachy team,
> > >
> > > I am trying to submit a patch using `git send-email --to
> > > outreachy@lists.linux.dev` with a few other emails cc'd.
> > >
> > > My SSL version is: 2.085
> > >
> > > When I am send the mail, I get the following error:
> > > > DEBUG: .../IO/Socket/SSL.pm:851: local error: SSL connect attempt failed error:0A00010B:SSL routines::wrong version number
> > > > DEBUG: .../IO/Socket/SSL.pm:854: fatal SSL error: SSL connect attempt failed error:0A00010B:SSL routines::wrong version number
> > >
> > > I am on Arch Linux, and I have installed the correct version with:
> > > cpan Authen::SASL, and installed the correct perl package:
> > > perl-io-socket-ssl 2.085-1
> > >
> > > My .gitconfig looks like this:
> > > [sendemail]
> > > smtpencryption = ssl
> > > smtpserver = smtp.gmail.com
> > > smtpuser = saashaa1122@gmail.com
> > > smtpserverport = 587
> > > confirm = auto
> > > supresscc = self
> > >
> > > [user]
> > > name = Saasha Gupta
> > > email = saashaa1122@gmail.com
> > > [core]
> > > editor = vim
> > > compression = 0
> > >
> > > I am not exactly sure why this issue is popping up, as all the
> > > required dependencies are installed. Can you please point me to where
> > > I might be going wrong?
> > >
> > > PS: Regarding the previous mail, I have solved all the problems, and
> > > created a patch.
> >
> > Hi Saasha,
> >
> > A couple of thoughts here. I'm not familiar w your SSL version issue,
> > maybe google that specifically.
> >
> > - https://man.archlinux.org/man/git-send-email.1.en suggests using tls
> >
> > - And as a work-around, if you have used git format-patch and have the
> > patch file ready to mail...you can simply do "mutt -H yourpatchname.patch"
> > When it opens in mutt you can edit the To/Cc if needed.
> > Send to yourself first to test.
> >
> > --Alison
> >
> >
> > >
> > > Thanks, Saasha
next prev parent reply other threads:[~2024-04-01 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 17:13 unable to submit patch with git send email Saasha Gupta
2024-04-01 17:45 ` Alison Schofield
[not found] ` <CAN=P6FPOSOW6uKoYrmEB_7tHub8Ba09Vftjw0eeniL_MK01CPw@mail.gmail.com>
2024-04-01 19:29 ` Alison Schofield [this message]
[not found] ` <CAN=P6FOtZUeOGKPSBP4gTUH3aAQc_AF8nN9AWCOWELEB2_1WpQ@mail.gmail.com>
2024-04-01 21:16 ` Alison Schofield
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=ZgsLAL2sELdJ9/h2@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=outreachy@lists.linux.dev \
--cc=saashaa1122@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.