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 17:14:52 +0200 [thread overview]
Message-ID: <20180515171452.78b8d170@windsurf> (raw)
In-Reply-To: <CAPi7W82SzgTdc+i20=pDWhgJA7qqTrrUu16BnEFeqONckzZ+vA@mail.gmail.com>
Hello,
On Tue, 15 May 2018 16:59:41 +0200, Fabrice Fontaine wrote:
> > OK, that explains the Git-formatted patches, without any obvious
> > upstream Git repository available online.
>
> So, do you want to reformat my patch? What is the best practice, should we
> always send git formatted patch even if there is no official Git
> repository?
The only clear policy that I'm trying to enforce is "if the project
uses Git as its version control system, then we want Git-formatted
patches". If on the other hand the projects is not using Git, then we
don't have a clear policy, and so far we have been accepting patches
that are not Git-formatted in such a case.
The snort situation caught my eye because your patch was not
Git-formatted, but the existing patches were.
> > OK, too bad. Is snort unmaintained ? Is upstream focused on this snort3
> > project ?
> >
> Actually snort is most widely used than snort3. snort3 is still in alpha. I
> have a patch for snort3 package but snort and snort3 don't use the same
> version of daq library :-/
We could have a separate snort3 package, and a separate package for the
daq library as well. If the daq libraries are API incompatible, it
makes sense to have two separate packages for them.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-15 15:14 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
2018-05-15 14:28 ` Sergio Prado
2018-05-15 14:59 ` Fabrice Fontaine
2018-05-15 15:14 ` Thomas Petazzoni [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=20180515171452.78b8d170@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 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.