Live data from Hacker News

A Git query language

github.com

1–10 of 72 posts

Re: A Git query language

#4
This is pretty cool. Looks like it's local to the current repo which makes sense for most usage. Having something like this across a swathe of repos would be useful in different ways (ex: "What has Bob committed over all the repos for our projects that involves the string 'billing'?".

Minor off topic rant about the animated example: Who doesn't put a space at the end of their prompt after the $?! Ugh!

Re: A Git query language

#5

A Git query language (github.com) 10 points by bryanrasmussen 1 hour ago This ought to have (2014) in the title: Latest commit 49c1c17 on 22 Jun 2014.

That makes it even more interesting, I mean the fact that this or something similar didn't get traction. I often have an idea of what I would like to know about my repo, but don't want to start hacking the answer together.

Re: A Git query language

#6
Imagine if we could just have this automatically for every program that generated text output. It doesn't seem beyond the realms of possibility that every tool could either a) structure its text output in a way that can guarantee simple command-piping to a general purpose query-language processing tool or b) in the presence of a "--output-json" flag, produce json which can then easily be queried.

Re: A Git query language

#7

Imagine if we could just have this automatically for every program that generated text output. It doesn't seem beyond the realms of possibility that every tool could either a) structure its text output in a way that can guarantee simple command-piping to a general purpose query-language processing tool or b) in the presence of a "--output-json" flag, produce json which can then easily be queried.

Sounds like you'd like the object-based Powershell.

Re: A Git query language

#9

Imagine if we could just have this automatically for every program that generated text output. It doesn't seem beyond the realms of possibility that every tool could either a) structure its text output in a way that can guarantee simple command-piping to a general purpose query-language processing tool or b) in the presence of a "--output-json" flag, produce json which can then easily be queried.

Or you could have a single address space (https://en.wikipedia.org/wiki/Single_address_space_operating...), and share objects directly.
Post reply on HN