omatic control and validation is required, do it
during the explicit tagging stage?
What is the goal of pre versioning?
[1] The fact that I can't look in the code for __version__ gives me
rage face.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode:
://review.openstack.org/#/c/286253
Avoid redundancy in header values
* https://review.openstack.org/#/c/276709
Added tags restrictions to the tagging guidelines
* https://review.openstack.org/#/c/243429
Add version discover guideline for API microversions
--
Chris Dent (�s°□°)�s�喋擤ォ
o hang out in
#openstack-infra so if anybody wants to discuss it ping me there.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
f we
have a system where we're having to do claims, instead of just
reflecting reality (i.e. real usage), things will go wrong, quickly.
We're much better figuring out a simpler system that includes the
possibility to fail fast.
[1] The proposed spec: https://review.openstack.
tests,
once we have them running against Python 3 is going to be quite
the problem and even if we fix this minor problem now, we're going
to have a much bigger one later (unless eventlet matures).
Does anyone else have additional ideas or thoughts.
--
Chris Dent (�s°□°)�s�喋擤ォ
On Wed, 16 Mar 2016, Jeremy Stanley wrote:
On 2016-03-16 13:55:56 + (+), Chris Dent wrote:
I built an IRC bot
https://anticdent.org/purple-irc-bot.html
[...]
Oof, a gerritbot derivative... at least it's not based on
supybot/twisted so doesn't suffer the IPv6+SSL issue we have
runs on and logs to the same
little pet where I run my blog and a few other things.
Let me know.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
On Mon, 14 Mar 2016, Chris Dent wrote:
wsgi-intercept (I maintain that) can use httplib2, http.lib or
requests (and if you go back a few versions even more) so those tests
could be updated to use requests and still use wsgi-intercept if that
was desired.
I've just released a version of wsgi
On Wed, 16 Mar 2016, Chris Dent wrote:
This review demonstrates a fix for the py34 unit tests sometimes
taking an age in the gate and eventually timing out:
https://review.openstack.org/#/c/293372/
The changed test, without the change, will block in epoll() for a
rather long time (900s
in thus far are just experiments. Nobody has
stepped up and said either of:
* "This is something we should make sure we have around"
* "I'd want this to be around if we just added feature X"
If there's not, I can avoid all that and continue using it for my own
purp
as I can tell. Thus removing a lot
of magical things that happen.
You can still get to the side-by-side view by pressing some buttons,
if you need to for some reason.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
On Tue, 15 Mar 2016, Markus Zoeller wrote:
Chris Dent <cdent...@anticdent.org> wrote on 03/15/2016 03:23:42 PM:
My take is that if we do have that level of friction then influence, in
its many forms, will solely be mediated by the vendors that consume the
upstream OpenStack community, or
and flow of the bug handling on its
own flow: something that anybody can do in the gaps of whatever else
they are doing without regard to the cycle's handling of features.
But yes, some kind of expiration of the backlog would be great. I'll
start doing what I can when I see it.
--
Chris Dent
chival value. It should go off the radar. Having a
bunch of stuff that looks like it needs to be done but never
actually is is stop energy and depressing.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
, the interface is much the same
Small enough that I wouldn't except any speedbumps.
However, there's no compelling reason to do so (yet) in the sense of
"it ain't broke".
Or are you saying that you think it is?
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org
b3 because the reason httplib2 was chosen is because it does
very little for you and makes few guesses. Requests on the other
hand... However there are no immediate plans to make any changes.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freen
will
contact him.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions
earlier in the thread, isn't
it the case that if you aren't using the service catalog to find an
endpoint, you're doing it wrong?
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
cloudkitty
cue
ekko
glance
ironic
magnum
mistral
radar
solum
surveil
terracotta
watcher
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
te the bad behavior. Upgrading to a new WSME breaks their
tests.
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent tw: @anticdent__
Open
as people provide them (and we become aware of them) and
we can continue to hassle Doug Hellman to make a release when one is
necessary but this does little to address the three gaps above nor the
continued use of the framework in existing projects.
Ideas?
Thanks.
--
Chris Dent (�s°□°)�s
/243041/
* https://review.openstack.org/#/c/243429/
)
Thanks.
[1] http://specs.openstack.org/openstack/api-wg/process.html#review-process
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
/api-wg/guidelines/http.html#use-of-501-not-implemented
501 isn't something api code should be intentionally generating.
400 or 404 is probably what you want.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
for your input.
[1] https://review.openstack.org/#/c/280381/
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack
things like 'Etag: 0' are used to say "Only
let this PUT happen if it is a create." That's a bit of a hack but
is useful.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
thing and has nothing to do with either REST or HTTP.
[1] https://tools.ietf.org/html/rfc7230#section-2.7.3
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
scheduling).
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions)
U
expensive, but it would be nice if the patrons (our
employers) would recognize that getting us all working well together
is a cost of doing this business.
Virtualized gatherings are useful too, but they don't accomplish the
same thing.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://ant
conversation I've been confused
by the apparent overlap or conflation of the API's interface and the
command line client's interface.
I agree that the API should be explicit and that the command line
should have sane defaults that don't violate the principle of least
surprise.
+1
--
Chris Dent
saging
nor with the way we track shared resources (resource-pools ought to
help).
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent tw: @anticdent__
?
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
omments merely as observations, with good intent and in good humor.
[1] https://review.openstack.org/#/c/281463/
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent
cts we could do even better at cross project things (as a
result of fewer combinations).
Also that growth should not be considered a good thing in and of itself.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://
one where
resources are not scarce.
The advantage of a centralized datastore for that information is
that it provides administrative control (e.g. reserving resources for
other needs) and visibility. That level of command and control seems
to be something people really want (unfortunately).
--
Chris Dent
n increasing the fog because cross-project concerns (which
help unify the vision and actuality that is OpenStack) get less
attention and the cycle deepens.
[1] Other people, some reasonable, some not, will have different
opinions. Yay!
--
Chris Dent (�s°□°)�s�喋擤ォ�http://ant
OpenStack nor for it to exist as
a valuable part of the open source world.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
Open
. That's an issue between the deployers and the users.
OpenStack has built in the protections, if people just to use them
poorly, their problem.
The original stated goal of this simpler neutron api was to get back
to the simpler nova boot. I’d like to see that happen.
+1
--
Chris Dent
On Wed, 10 Feb 2016, Sean Dague wrote:
If there are concerns with this approach let me know. Otherwise I'll
propose the repo tomorrow and try to keep this ball rolling.
+1. It's a good plan. Thanks for keeping the distillery cooking.
--
Chris Dent (�s°□°)�s�喋擤ォ�http
On Tue, 9 Feb 2016, Chris Dent wrote:
eventlet 0.18.2 has broken the nova unit tests at
'nova.tests.unit.test_wsgi.TestWSGIServerWithSSL' so the gate is
blocked.
sdague et al are working on it. Please hold off approving patches
in nova until they get it resolved.
Just in case it's
It's eventlet release day!
eventlet 0.18.2 has broken the nova unit tests at
'nova.tests.unit.test_wsgi.TestWSGIServerWithSSL' so the gate is
blocked.
sdague et al are working on it. Please hold off approving patches
in nova until they get it resolved.
--
Chris Dent (�s°□°)�s�喋擤
uff under the tent works well with the rest of the world by virtue
of being a part of it rather than a separate something that is growing
to consume everything it needs). The tent doesn't have to cover
everything.
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-February/085748.html
--
the service catalog
As discussed elsewhere 3 is a feature not a bug. We should endeavor
to keep the service catalog clean, tidy, and limited as a control on
OpenStack itself is clean, tidy and limited.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.
around the edges of a referendum on
the "duplication" aspect of the big tent.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent
4]
http://specs.openstack.org/openstack/openstack-specs/specs/service-catalog.html
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
to the project
acceptance criteria, but I'm in the minority it seems in this thinking.
I can get behind that.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
APIs when re-using real users' client code amongst a
diversity of clouds
Just those two things can help us evaluate proposals with some
useful constraints.
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent
he selling worry about the market, if they
want. That stuff is, or at least should be, on the other side of a
boundary.
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent
copyright notifications in files.
I'd also be happy to see all the existing ones removed, but that may
be a bigger problem.
If I was the only person to choose, I'd say let's go for 1/, but
probably managers of every company wont agree.
I think option one is correct.
--
Chris Dent (�s
k.org/wiki/API_Working_Group#Purpose
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage
: In the hands of the main developers of
any project. Please just make sure that any app that is created can
be hosted by any reasonable WSGI host.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
in the comments, discussing various
alternatives.
Thanks.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development
pairs that can be created
and extended either programmatically or through a declarative file[3].
[2] https://pypi.python.org/pypi/selector
[3] A reasonable example from the past:
https://github.com/tiddlyweb/tiddlyweb/blob/master/tiddlyweb/urls.map
--
Chris Dent (�s°□°)�s�喋擤ォ
s like it could in others.
[1]
https://review.openstack.org/#/c/266211/1/ceilometer/tests/unit/image/test_glance.py
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
shouldn't use a private method?
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage
that gnocchi does does not help
the use case. The one way translation is used in the body of search
queries as well as in any URL which contains a resource_id.
I'm sure there are use cases where it breaks down, but I've not
heard them enumerated explicitly.
Thanks.
--
Chris Dent (�s°□°)�s�喋擤ォ
delegate the chosen resource to, for example, Ironic.
That ^ makes me think of this: https://review.openstack.org/#/c/253187/
Seem to be in at least similar veins.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent tw
of the interface you can do whatever you like in the
guts.
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development
(establishes backend stuff):
https://github.com/openstack/gnocchi/blob/master/gnocchi/tests/gabbi/fixtures.py
and the yaml test files themselves:
https://github.com/openstack/gnocchi/tree/master/gnocchi/tests/gabbi/gabbits
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org
lly.
Nor should we be building formalisms that are defenses against an
architecture that's sub-optimal. We need to evolve the formalisms and
the architecture toward the ideal.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
n't really that important.
I reckon (and this may be an emerging consensus somewhere in this
thread) we need to make it easier (by declaration) in the tooling
to test against whatever is desired. Can we enumerate the changes
required to make that go?
--
Chris Dent (╯°□°)╯︵┻━┻
is because of availability. It's fairly understood that zookeeper
would be more correct but there are packaging concerns.
--
Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/
freenode: cdent
On Thu, 5 Nov 2015, Sean Dague wrote:
On 11/05/2015 03:08 AM, Chris Dent wrote:
Outside of CI it is possible to deploy ceilo, aodh and gnocchi to use
tooz for coordinating group partitioning in active-active HA setups
and shared locks. Again the standard deploy for that has been to use
redis
://specs.openstack.org/openstack/ceilometer-specs/specs/kilo/declarative-http-tests.html
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage
On Tue, 15 Sep 2015, Zhai, Edwin wrote:
I saw some patches from Chris Dent to enable functions in devstack/*. But it
conflicts with devstack upstream so that start each ceilometer service twice.
Is there any official way to setup ceilometer as devstack plugin?
What I've been doing
' attribute being
dropped.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
nd has
all the pollsters installed but not all started by default.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
On Wed, 9 Sep 2015, Chris Dent wrote:
On Wed, 9 Sep 2015, Chris Dent wrote:
I'll push up a couple of reviews to fix this, either on the
ceilometer or devstack side and we can choose which one we prefer.
Here's the devstack fix: https://review.openstack.org/#/c/221634/
This is breaking
updates[3].
I'll push up a couple of reviews to fix this, either on the
ceilometer or devstack side and we can choose which one we prefer.
[1] https://review.openstack.org/#/c/212498/
[2] https://review.openstack.org/#/c/196383/
[3] https://review.openstack.org/#/q/topic:bug/1489436,n,z
--
Chris
You can work around the problem by replacing lines like:
enable_service ceilometer-acompute ceilometer-acentral
ceilometer-anotification ceilometer-collector ceilometer-api
with:
enable_plugin ceilometer git://git.openstack.org/openstack/ceilometer
in your local.conf
--
Chris Dent
On Wed, 9 Sep 2015, Chris Dent wrote:
I'll push up a couple of reviews to fix this, either on the
ceilometer or devstack side and we can choose which one we prefer.
Here's the devstack fix: https://review.openstack.org/#/c/221634/
In discussion with other ceilometer cores we decided
On Fri, 28 Aug 2015, Chris Dent wrote:
The problem with the spec is that it doesn't know what to replace
WSME with.
Thanks to everyone who provided some input.
The summary is: A lot of support for Flask. A fair bit of support
for the idea of using JSONSchema and publishing it.
Since
On Thu, 27 Aug 2015, Chris Dent wrote:
On Wed, 26 Aug 2015, Matthew Treinish wrote:
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n571
Is 'process_testr_artifacts' going to already be in scope for the
hook script or will it be necessary to source functions.sh
specific comments on the spec please response there.
Thanks!
P.S: An option not listed, and one that may make perfect sense for
ceilometer (but perhaps not aodh), is to do nothing and consider the
v2 api legacy.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
is it?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
to typed input and output
handling and validation) by doing the HTTP handling that got the
desired results _not_ correct HTTP. It is riddled with incorrect
handling of headers and response codes that are very hard to fix
without causing unplanned side effects.
--
Chris Dent tw:@anticdent
minimum of checks to confirm that
the upgrade was successful (in devstack/upgrade/upgrade.sh).
Now that the plugin is in repo we have a lot of flexibility to do
whatever we want and we should.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
for posting about this.
I've gone through this morning and rebased some of the pending
patches that just needed a rebase to get moving.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack
, not accidental
behaviors that are present as a result of bugs.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
://review.openstack.org/#/c/208467/
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
stellar work to insure
stability. Thank you _very_ much. I'm arguing about the devstack
default.
And even then, I'm not arguing that we don't set it, rather that we
just pause a moment and think about the side effects, if any.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks
, but
not forgotten.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
the thread through its paces and getting the thinking out in the
open.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
up? I've got it on my schedule to come the week
after.
I suspect there's a lot we can do over the long run to avoid
duplicating code and effort but that there will be some humps to
ride over to different pieces (and people!) talking to one another.
Should be fun. Looking forward to it.
--
Chris
collaboration that can happen?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
/meetings/ceilometer/2015/ceilometer.2015-08-06-15.01.log.html#l-110
[2] directly as in aodh-notifier --config-file /etc/ceilometer/ceilometer.conf
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
On Fri, 7 Aug 2015, Julien Danjou wrote:
On Fri, Aug 07 2015, Chris Dent wrote:
If someone installs aodh on a machine that already has ceilometer on it
and turns off ceilometer-alarm-notifier and ceilometer-alarm-evaluator
(in favor of aodh-notifier and aodh-evaluator) will they be able
artifacts like database migration files so are not a super accurate
overview of true test coverage, just a (potentially) useful indicator.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack
with each session _in advance_ of the sessions.
This will help make sure we focus on the stuff that people actually
care about.
Some sessions currently have neither leader nor etherpad. We need to
fix that.
See you there.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
On Fri, 3 Jul 2015, Jeremy Stanley wrote:
On 2015-07-03 14:54:28 +0100 (+0100), Chris Dent wrote:
Does a virtual mid-cycle count? This one is not quite a sprint. It's a
bunch of meetings, held on google hangouts (falling back to other things
if it is junk), schedule over a two day period
On Fri, 3 Jul 2015, Jeremy Stanley wrote:
On 2015-07-03 10:07:05 +0100 (+0100), Chris Dent wrote:
The Ceilometer virtual mid-cycle will be held next week, the 9th and
10th of July.
[...]
Annoying but friendly reminder to please add it at
https://wiki.openstack.org/wiki/VirtualSprints when
On Fri, 26 Jun 2015, Chris Dent wrote:
Ceilometer contributors and other interested parties,
To keep people in the loop:
The Ceilometer virtual mid-cycle will be held next week, the 9th and
10th of July. The schedule is being worked out.
The topics that will be covered include:
* Getting
On Thu, 2 Jul 2015, Chris Dent wrote:
The voting related to the ceilometer mid-cylce is now closed. Prad and I
will work to come up with a proposed schedule.
Can interested participants please make sure they are up to date on
http://doodle.com/6vfksdu38wcwqqd3 with two consecutive days where
and
volunteer to lead if you like.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On Fri, 26 Jun 2015, Chris Dent wrote:
Ceilometer contributors and other interested parties,
It's been pointed out that the topic titles at
https://etherpad.openstack.org/p/ceilometer-liberty-midcycle
and the agenda items and descriptions at
https://etherpad.openstack.org/p
.
* If we deprecate will people bother to use the new stuff?
I'm sure there are plenty of others.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage
On Sat, 27 Jun 2015, Chris Dent wrote:
* What code should be calling and hosting install_ceilometermiddleware?
Since it is lib/swift that is using it, there makes some sense?
Especially since it already has a relatively long block of
configuration instruction.
I've put up a devstack
://etherpad.openstack.org/p/ceilometer-liberty-midcycle.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
/
* The start of the grenade plugin:
https://review.openstack.org/#/c/196441/
* Removing ceilometer from grenade:
https://review.openstack.org/#/c/196448/
Thanks!
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
with which to get that information because it is an actual
identifier, by definition.
I assume it is probably too late to go back and make this true
everywhere, but we should do what we can to make it real
GoingForward™.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks
501 - 600 of 758 matches
Mail list logo
