From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] snort: fix build on sparc v8
Date: Tue, 15 May 2018 14:41:28 +0200 [thread overview]
Message-ID: <20180515144128.602fea19@windsurf> (raw)
In-Reply-To: <CANu7NGtFKmJdQoT_-ecuUyG3Apctxm-6u7kjiYPeHOqkbk-L2w@mail.gmail.com>
Hello,
On Mon, 14 May 2018 13:56:29 -0300, Sergio Prado wrote:
> > However, I haven't been able to find an upstream Git repository for
> > Snort, so I'm wondering how the existing Git-formatted patches have
> > been generated. Perhaps from a repository created locally using git
> > init+git add ?
> >
> > Sergio, since you added the snort package, how did you generate the
> > patches ?
>
> Yes, I manually created the git repository to generate the patches.
OK, that explains the Git-formatted patches, without any obvious
upstream Git repository available online.
> I have also sent the patches upstream and ping one time after a
> month, but got no responses so far.
OK, too bad. Is snort unmaintained ? Is upstream focused on this snort3
project ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-15 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 11:17 [Buildroot] [PATCH 1/1] snort: fix build on sparc v8 Fabrice Fontaine
2018-05-13 13:55 ` Yann E. MORIN
2018-05-13 19:45 ` Thomas Petazzoni
2018-05-14 16:56 ` Sergio Prado
2018-05-15 12:41 ` Thomas Petazzoni [this message]
2018-05-15 14:28 ` Sergio Prado
2018-05-15 14:59 ` Fabrice Fontaine
2018-05-15 15:14 ` Thomas Petazzoni
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=20180515144128.602fea19@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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