From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Typo in /var/ipfire/langs/en.pl
Date: Tue, 06 Feb 2018 16:37:10 +0000 [thread overview]
Message-ID: <1517935030.21272.92.camel@ipfire.org> (raw)
In-Reply-To: <44f30b0c-5ef4-0fa6-09ad-5faf277bfcf9@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
It actually is just one line to send the patch in the end, but setting up the
entire build environment, building the distribution, making changes, getting an
image, installing the image, perform testing, repeat thing is quite long.
-Michael
On Tue, 2018-02-06 at 11:33 -0500, Tom Rymes wrote:
> Thanks, Michael. I was just confused as to just how complicated the
> process needed to be for such a simple fix.
>
> I'll spend more time sifting through the patch documentation.
>
> Tom
>
> On 02/06/2018 10:50 AM, Michael Tremer wrote:
> > Hi,
> >
> > I just fixed that very quickly for you:
> >
> > https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=cfa228c2f3c852ad6
> > f5829fddfffe1f49a1f98f0
> >
> > On Tue, 2018-02-06 at 10:38 -0500, Tom Rymes wrote:
> > > I was just poking around in Bugzilla and noticed this old bug I had
> > > created. https://bugzilla.ipfire.org/show_bug.cgi?id=10595
> > >
> > > Basically, it causes the names displayed for the Root and Host
> > > certificates on the IPSec page to have inconsistent capitalization
> > > ("Host Certificate" vs. "Root certificate").
> > >
> > > This is clearly not a big issue, but it's also an easy fix, and I
> > > thought "hey, I can fix this!" However, I'm not really certain what the
> > > best method would be to submit the change.
> > >
> > > Any suggestions as to where I can start?
> >
> > This is where the documentation about sending patches is:
> >
> > https://wiki.ipfire.org/devel/submit-patches
> >
> > Best,
> > -Michael
> >
> > >
> > > Tom
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-06 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:38 Tom Rymes
2018-02-06 15:50 ` Michael Tremer
2018-02-06 16:33 ` Tom Rymes
2018-02-06 16:37 ` Michael Tremer [this message]
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=1517935030.21272.92.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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