iodically" process. Both objects created by Xastir
and those that come in through an interface get treated the same way. But I'd
actually have to revisit all the code to make sure this is true.
And I'm pretty sure that non-object/item packets don't get the same treatment.
> On Thu,
The code is pretty hard to read and is peppered with blocks of commented-out
code that have been that way since 2005. There used to be some attempt to
treat the injected stuff as third-party only if its callsign was different
from Xastir's, but all that is commented out and stuff injected by
On Sun, Dec 19, 2021 at 02:37:24PM -0800, we recorded a bogon-computron
collision of the flavor, containing:
> Ah, should have read everything more thoroughly... So by adding
> another library to Linux we might be able to use something better.
I disagree: by adding another library, we're
I have created a pull request on github with the changes needed to documentation
to implement this simplified release process.
When you and Curt have reviewed it, please merge it and I'll move with actually
doing the point release.
Doing the point release this way is very little more than
On Thu, Sep 03, 2020 at 09:57:50AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Roger. Thanks Tom.
>
> To the other Tom: Try deleting that file from the scripts directory
> and checking the file out again from Git, then a make clean;make;make
> install to see if
rk
is the way to make a mess.
> On Fri, Apr 17, 2020 at 3:00 PM km5vy Tom Russo wrote:
> >
> > On Fri, Apr 17, 2020 at 02:58:47PM -0700, we recorded a bogon-computron
> > collision of the flavor, containing:
> > > I should run through the wx alert files real quick too.
On Fri, Apr 17, 2020 at 08:54:30AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Sure.
I can do that tonight if we're all in accord. It's a fairly lightweight
process anymore to push out a release on github.
> On Fri, Apr 17, 2020 at 8:33 AM Tom Russo wrote:
> >
uot;
> On Tue, Mar 24, 2020 at 9:45 AM km5vy Tom Russo wrote:
> >
> > On Tue, Mar 24, 2020 at 09:41:49AM -0700, we recorded a bogon-computron
> > collision of the flavor, containing:
> > > Yea, try it... I didn't see any filenames listed in the output.
> >
how dbfawk_load_sigs works.
Which seems a lot more work than running testdbfawk and using standard linux
tools to find all matching files. The only reason for doing this is to find
all the files other than the one you WANT to use that may be used instead.
And it can be done now with no hacking.
> &
fig/*
to get the list of file names that contain that signature.
> On Tue, Mar 24, 2020 at 9:34 AM km5vy Tom Russo wrote:
> >
> > On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a bogon-computron
> > collision of the flavor, containing:
> > > On Tue
On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> On Tue, Mar 24, 2020 at 9:13 AM Curt Mills wrote:
> >
> > One could also turn on debug level 16. Might be of use in this case.
>
> Could also mess around with testdbfawk, although now
On Mon, Jul 15, 2019 at 08:37:14AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Or delete the user and create a fresh account?
There is apparently no longer a way to delete a user from the web interface
anymore, either:
On Sun, Jul 14, 2019 at 02:54:31PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> I could slam out a 2.1.4 release real quickly tonight if we think it's
> worth the good will of package maintainers.
>
> Here's what I see as the changes since 2.1.2:
>
> - Code
I could slam out a 2.1.4 release real quickly tonight if we think it's
worth the good will of package maintainers.
Here's what I see as the changes since 2.1.2:
- Code reformatting to match new project style
- Numerous updates to decrease number of warnings from gcc8
- Fix compiler
before telling
Xastir about the images (using GDAL command line tools).
> On Fri, May 31, 2019 at 2:43 PM km5vy Tom Russo wrote:
>
> > On Fri, May 31, 2019 at 02:29:36PM -0500, we recorded a bogon-computron
> > collision of the flavor, containing:
> > > So, a question. I'
;
> On Thu, May 30, 2019 at 12:38 PM Curt Mills wrote:
>
> > Rgr. Will post announcement today then.
> >
> > On Thu, May 30, 2019 at 10:33 AM km5vy Tom Russo
> > wrote:
> >
> > > On Thu, May 30, 2019 at 11:12:03AM -0600, we recorded a bogon-comput
;
> On Thu, May 30, 2019 at 12:38 PM Curt Mills wrote:
>
> > Rgr. Will post announcement today then.
> >
> > On Thu, May 30, 2019 at 10:33 AM km5vy Tom Russo
> > wrote:
> >
> > > On Thu, May 30, 2019 at 11:12:03AM -0600, we recorded a bogon-comput
On Thu, May 30, 2019 at 11:12:03AM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Mon, May 27, 2019 at 11:52:53AM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > Fine by me. I can do all the announcements.
>
> It is likely that
On Mon, May 27, 2019 at 11:52:53AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Fine by me. I can do all the announcements.
It is likely that I'll go ahead and walk through the git steps of doing
the release tonight instead of tomorrow. My "friday off" turns out
On Mon, May 27, 2019 at 11:52:53AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Fine by me. I can do all the announcements.
It is likely that I'll go ahead and walk through the git steps of doing
the release tonight instead of tomorrow. My "friday off" turns out
On Tue, Apr 30, 2019 at 12:41:50PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Tue, Apr 30, 2019 at 11:14:54AM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > What do you think of this idea instead: https://editorconfig.org/
>
On Tue, Apr 30, 2019 at 11:14:54AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> What do you think of this idea instead: https://editorconfig.org/
> It requires a plug-in for Emacs and VIM, but we could add that to the
> coding standards.
I'm not particularly keen
Seconded.
I think that the people who established the current standard for Xastir
are long gone, and maintaining consistency with that style for the sake
of consistency has gone on long enough.
I personally hate *both* the four-space indentation *and* the
"egyptian brace"/K style, and prefer
On Tue, Apr 30, 2019 at 08:09:21AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Yes on the NWS script being up-to-date. With all the places the code has
> been tweaked recently I'd like to see the dust settle for a few weeks. Give
> us time to test out all the
On Tue, Apr 23, 2019 at 08:35:12PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Your thinking on distributions to drop is sound. It's what I would want as
> well.
>
> For the gcc-8 build should we add those two flags as well?
Perhaps, unless you really want to
y, since your commits
were mooted in upstream.
> On Mon, Apr 22, 2019 at 9:33 AM km5vy Tom Russo wrote:
>
> > On Mon, Apr 22, 2019 at 09:28:14AM -0700, we recorded a bogon-computron
> > collision of the flavor, containing:
> > > However I didn't rebase. I only di
On Tue, Apr 16, 2019 at 08:35:30AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> I was thinking about that github:xastir/Xastir page in terms of a
> first-time user: They want instructions for compiling and getting it
> running RIGHT NOW. They don't care about 95%
On Mon, Apr 15, 2019 at 12:51:01PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> On Mon, Apr 15, 2019 at 10:03 AM Tom Russo wrote:
> >
> > On another note, I'd really like someday to do away with our "internal
> shapelib"
> > because it's an artifact of the bad old
On Thu, Aug 18, 2016 at 03:17:49PM -0400, we recorded a bogon-computron
collision of the <david.aitche...@gmail.com> flavor, containing:
>
>
> On 08/18/2016 02:35 PM, km5vy Tom Russo wrote:
> > On Thu, Aug 18, 2016 at 11:06:08AM -0700, we recorded a bogon-computron
> &g
On Thu, Aug 18, 2016 at 11:06:08AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> On Thu, Aug 18, 2016 at 10:57 AM, Tom Russo wrote:
>
> >
> > Well, there go any theories I might have had. If your source is current,
> >
On Thu, Jul 07, 2016 at 01:17:45PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron
> collision of the flavor, containing:
> > Just trying it out --
On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron
collision of the flavor, containing:
> Just trying it out -- checked out the repo, bootstrap.sh, ./configure, make
>
> Unfortunately:
>
> make[2]: *** No rule to make target `README.CVS', needed by
On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron
collision of the flavor, containing:
> Just trying it out -- checked out the repo, bootstrap.sh, ./configure, make
>
> Unfortunately:
>
> make[2]: *** No rule to make target `README.CVS', needed by
On Thu, Mar 17, 2016 at 07:34:00AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
>
>get-maptools.sh:
>** 50 different Wiki pages!!! What?
There are many pages that are just version-specific deltas off of an old
Debian install HowTo,
On Thu, Oct 29, 2015 at 04:06:43PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Thu, Oct 29, 2015 at 03:53:46PM -0600, we recorded a bogon-computron
> collision of the flavor, containing:
> > On Thu, Oct 29, 2015 at
On Thu, Oct 29, 2015 at 02:41:04PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> On Thu, Oct 29, 2015 at 2:24 PM, Tom Russo wrote:
> > Please try the following:
> > - edit configure.ac in the Xastir source tree, and find the
On Thu, Oct 29, 2015 at 03:53:46PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Thu, Oct 29, 2015 at 02:41:04PM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > On Thu, Oct 29, 2015 at 2:24
37 matches
Mail list logo