IRC log for #neo900 on 20161219

00:00.07wpwraknow we need also need a process that can move a little from A to B. but that "a little" has slightly different characteristics than the things in "everything"
00:00.17*** join/#neo900 atk (~Arch-TK@fsf/member/Arch-TK)
00:00.20Joerg-Neo900o.O
00:01.14wpwrakso we have to see what the impact of these differences is. maybe it's negligible. maybe we hit unexpected issues, like today. maybe it turns out to be very hard, harder than what we solved today.
00:01.18Joerg-Neo900now that made it absolutely clear ;-)
00:02.05wpwrakin the latter case, a fallback solution could be to just re-generate periodically or such. that would create certain issues, too, though. so that needs to be evaluated.
00:02.25Joerg-Neo900please don't overengineer!
00:02.32wpwrakin any case, atk seems to be optimistic that it's now smooth sailing. i never worked with those hooks while he has.
00:03.04Joerg-Neo900we don't need hooks to populate the empty ee repo with what's already there in ee-full
00:03.15Joerg-Neo900we only need to run that job, no?
00:03.35Joerg-Neo900hooks will be needed when somebody does next push
00:03.46wpwrakyes
00:04.11Joerg-Neo900so, why don't we already populate the repo with what we got so far?
00:06.12wpwrakbecasue there are more details missing. e.g., the definition of the committer. the committers influences the hash. if the committer changes, and the repo needs regenerated, all hashes change too. this will cause git to freak out for everyone who has cloned the repo.
00:06.35wpwrakso as i said, we can do that, but it's not very civilized
00:06.43Joerg-Neo900ok, so the big job is not ready for primetime. Simple answer
00:06.59*** join/#neo900 louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
00:07.01wpwrakprecisely
00:07.11*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
00:07.46Joerg-Neo900it seems my brain isn't fit anymore for elaborate long answers, neither for "simple" ones with little things and big things
00:08.52wpwraka nap may help :) or, in my case, dinner ... and then a nap (plumbers announced their visit for tomorrow. of course, that probably means that i'll wait in vain, once again)
00:09.17Joerg-Neo900I'm pretty sure it's not a nap that's needed here
00:10.01wpwrakseep helps to detox (chemically) the brain. that's scientifically proven :)
00:10.04Joerg-Neo900it's probably I never will adopt that terminology and view to the world that comes with excessive use of git
00:10.06wpwraksLeep even
00:10.58wpwrakyes, it was all easier with steam-driven punchcard readers :)
00:11.13Joerg-Neo900or simply put: I git this wrong: [2016-12-19 Mon 00:21:09] <wpwrak> yeah ! so we now recreate a perfect copy of the "censored" repo
00:11.32Joerg-Neo900got even
00:11.39wpwraknice freudian ;-))
00:11.51Joerg-Neo900no, mechanical failure
00:12.09Joerg-Neo900I got motoric issues
00:12.58wpwrakyup, we have the copy. now we just have to make sure it stays current. plus a script or two to wrap it all up.
00:13.22Joerg-Neo900you just said we don'
00:13.23Joerg-Neo900t
00:13.46Joerg-Neo900sorry, this is too bizarre for me now
00:13.46wpwrakanyway, that's for tomorrow
00:19.12Joerg-Neo900either we got a perfect copy then it's ok to have it available via webgit for public, and it will not even be a drama when there might be a push of new stuff in two days since we could re-initialize and resync the whole thing in no time. Or the copy is not yet perfect then I got a two or three statements wrong
00:20.33Joerg-Neo900anyway I'd like to have *some* content on webgit rather sooner than later
00:21.02Joerg-Neo900it's pretty embarrassing to have an empty repo that we made such fuzz about all the time
01:35.23*** join/#neo900 knttl (~knttl@host-091-097-091-040.ewe-ip-backbone.de)
01:42.46*** join/#neo900 xes (~xes@unaffiliated/xes)
03:19.00*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
03:54.33*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
04:06.18*** join/#neo900 xmn (~xman@user-0cdft6f.cable.mindspring.com)
04:30.38*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
04:46.49*** join/#neo900 xmn (~xman@user-0cdft6f.cable.mindspring.com)
05:05.40*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
05:38.54*** join/#neo900 neo900 (~office@neo900/coreteam/joerg)
05:38.54*** mode/#neo900 [+v neo900] by ChanServ
05:38.57*** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
05:38.57*** mode/#neo900 [+v DocScrutinizer05] by ChanServ
05:42.47*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
06:17.49*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
06:58.45*** join/#neo900 tsuggs (~tim@adsl-074-171-024-060.sip.int.bellsouth.net)
07:02.27*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
08:05.50*** join/#neo900 qwazix (~qwazix@Maemo/community/ex-council/qwazix)
08:06.47*** join/#neo900 silviof (~silviof@unaffiliated/silviof)
08:13.33*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
08:49.04*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
09:02.53*** join/#neo900 qwazix (~qwazix@Maemo/community/ex-council/qwazix)
09:18.23*** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr)
09:26.09*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
09:46.11*** join/#neo900 treeman (~treeman@84.217.173.228)
09:49.54*** join/#neo900 jonsger (~Thunderbi@HSI-KBW-046-005-000-118.hsi8.kabel-badenwuerttemberg.de)
09:55.42*** join/#neo900 cc___ (~ac@2001:910:113f:1:6a05:caff:fe1c:1627)
10:01.41*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
10:05.56*** join/#neo900 galiven__ (~Andrew@50-205-116-131-static.hfc.comcastbusiness.net)
10:14.15*** join/#neo900 Pali_ (~pali@Maemo/community/contributor/Pali)
11:08.43wpwrakJoerg-Neo900: agreed. i was quite surprised to see you guys "pull the plug".
11:09.58wpwrakhow900, atk: now, about setting the committer name. do you know if there is any sort of convention the kind of automated committer we'd have in this case ?
11:13.19*** join/#neo900 goiken_ (~goiken@dslb-094-223-166-250.094.223.pools.vodafone-ip.de)
11:15.09wpwrakfrom what i gather, having an e-mail address (at least syntactically) in there, is required. (e.g., the behaviour of "git commit --author=AUTHOR" strongly suggests this)
11:24.21*** join/#neo900 mzki (~koza@89-76-126-150.dynamic.chello.pl)
11:32.44*** join/#neo900 jefrite (U2FsdGVkX1@ma.sdf.org)
11:38.35*** join/#neo900 SylvieLorxu (~TheLastPr@541B7AAC.cm-5-4b.dynamic.ziggo.nl)
11:40.58how900wpwrak: it's set with git config user.name foo ; git config user.email foo@bar.com
11:41.24how900wpwrak: so the git config of the user running the script, or for each commit...
11:46.52*** join/#neo900 jonsger1 (~Thunderbi@188.95.51.186)
11:49.42*** join/#neo900 jonsger (~Thunderbi@178.209.52.74)
12:09.58*** join/#neo900 jonsger1 (~Thunderbi@46.23.72.209)
12:38.43wpwrakhow900: yes, in our case, there isn't really a proper "user" who is the committer (well, if someone runs things manually, then there technically is, but that's spurious). so it would be nice to use something a) less misleading, and b) properly reproducible
12:39.03Wizzupcan I ask approx how many orders does neo900 have atm?
12:39.59wpwrakhow900: could be "whatever <nobody@neo900.org>", or such. so i wonder if there's some precedent for such names we could follow, or if we get to make up our own
12:40.43wpwrakhow900: another option could be to use the author for the committer. but it seems that this would require more elaborate tweaking.
12:55.25wpwrakmaybe something like "Generated from internal repo <nobody@neo900.org>" ? (to indicate 1) that it's not a true source, 2) that it's no a proper subset either, 3) roughly where it comes from. i.e., it's basically what you'd expect of a regular repo, but you'll find quirks if you look really closely)
13:00.16wpwrakWizzup: should be around 350, i think
13:00.29Wizzupcool, thanks
13:00.38Wizzupso for the final prod you are looking for 450 more
13:03.28how900Wizzup: yup
13:03.54how900anyone going to 33c3?  We should organize a meeting...
13:07.59WizzupI am not - already had other (hard to change/family) plans, and no ticket
13:46.04atkwpwrak: 350 now? that sounds like it has gone up from 250 since a good while ago.
13:46.12atkwpwrak: is the target still 500 or has that gone up?
13:48.12atkwpwrak: I could have a look at what committer info linux has for pre-bitkeeper times
13:48.23wpwrakatk: it was some ~320 a year ago. so that's +10%, with only collateral PR (i.e., hellekin's newsletters sometimes motivate lurkers. but we haven't really tried to reach out to new people in 2016)
13:48.38atkah
13:49.04atkLinux-2.6.12-rc2 is the earliest commit in mainline
13:49.14atkThey didn't bother importing history before that.
13:49.28bencohiirc there'is a history tree
13:49.41wpwrakgrr. so how will i build my 0.12 kernel now ?
13:50.17bencohhttp://git.kernel.org/cgit/linux/kernel/git/tglx/history.git
13:51.06atkLinus is the committer in the few I've just looked at.
13:51.14atkhmm
13:51.14wpwrakCommit:     Linus Torvalds <torvalds@ppc970.osdl.org>
13:51.18wpwrakyup
13:51.20atksome others have other committers
13:51.26atkit just seems like the committers were preserved there
13:51.38atkI guess linus applied patches way back when
13:51.51bencohwpwrak: https://git.kernel.org/cgit/linux/kernel/git/history/history.git/commit/?h=0.12&id=2ab763b2e26be65551e717bd547497ffb9ba7267 ;P
13:52.05bencoh(now back to my jtag)
13:52.12atkJust make the committer "Auto Commit <nobody@neo900.org>"
13:52.47wpwrakbencoh: thanks ;-)
13:54.16atkI'm impressed that the history stretches that far back.
13:55.02atkand if you host this on cgit, explain in the "about" page that this tree is a copy tracking the internal tree and why some parts are being temporarily censored.
13:55.08atkAnyway, I need to go, see you this afternoon.
14:14.59wpwrakJoerg-Neo900: does "Generated from internal repo <nobody@neo900.org>" for the committer sound okay ? once we've picked a name, i'll process "ee-full" with it and push it into "ee" on neo900.org/git
14:18.21ceenewonders why are you doing such strange things
14:26.07wpwrakceene: the filtering ? because joerg doesn't want the kicad_pcb file(s) to appear in the public ee repo. so we need to filter this from ee-full.
14:26.12*** join/#neo900 SylvieLorxu (~TheLastPr@145.48.120.201)
14:26.30ceenei thought the way to do that was gonna be gitolite partial copy
14:30.09Joerg-Neo900wpwrak: yes
14:31.50wpwrakceene: naw, gitolite is the wrong layer. there, you can hide things from a web browser, but not from git clone
14:32.04wpwrakceene: i.e., you can hide it from a lawyer, but not from an engineer :)
14:32.49ceenepartial copy wouldn't copy just master branch, leaving aside all other commits not related to this branch?
14:34.05Joerg-Neo900I think it's partial-copy is poorly documented, fragile, and depends massively on discipline op committers
14:34.09Joerg-Neo900of
14:35.44Joerg-Neo900and you have no control over stuff a posteriori
14:36.22ceenethe kind of loops wpwrak seems to be doing doesn't look any less fragile, though
14:36.32ceenediscipline committer is a real issue, though
14:36.41ceenei've committed too many things i didn't want to commit
14:36.48ceene:/
14:37.54Joerg-Neo900ceene: we simply "copy" the complete repo, and we can apply filters during that
14:37.59Joerg-Neo900no loops
14:39.22ceenebut i wonder if git format-patch | git am the best way to do that...
14:44.12Joerg-Neo900well, it seems really simple, standard, and it's already tested and seems to do what we want
14:44.55ceenedon't know, i think i would have used filter-branch
14:45.49Joerg-Neo900the guys considered all that
14:46.05Joerg-Neo900don't worry, you won't notice either
14:46.58ceenein any case, "if it is working don't touch it", as the engineers' maxim says
14:48.57wpwrakceene: there are no loops now :) and it's git log, for the precious -m option. that's what makes it all work :)
14:50.43Joerg-Neo900and it works with scripts, which I like ;-)
14:51.02Joerg-Neo900it's so tangible
14:51.53wpwrakhttps://neo900.org/git/ee/tree    is alive again
14:51.56Joerg-Neo900scripts and hooks. A concept I'm *very* familiar with
14:52.59ceenegreat! :)
14:53.16wpwrakand in  https://neo900.org/git/ee/commit/  one can see that it is the work of our publication process
14:54.20ceenegood, author is preserved but committer is the automatic thing
14:54.22wpwraknote: there are no automatic updates yet. so until we set up this as well, it'll lag a little.
14:54.49ceenebtw, english is a very redundant language, committer has two double consonants
14:55.50Joerg-Neo900compared to arabic? ;-)
14:56.17wpwrakceene: i'll see your committer and raise you a mississippi
14:56.22ceene:D
14:58.40*** join/#neo900 jonsger1 (~Thunderbi@HSI-KBW-046-005-000-118.hsi8.kabel-badenwuerttemberg.de)
15:24.20*** join/#neo900 chomwitt (~chomwitt@athedsl-31537.home.otenet.gr)
15:25.34Joerg-Neo900wpwrak: re LEDs: we want a low Vfwd (so red?) high efficiency LED operated at a current of less than 1mA
15:27.08Joerg-Neo900ideally side looking, though that's not really mandatory
15:28.57Joerg-Neo900sorry, seems those are called "low current" not "high efficiency"
15:30.52Joerg-Neo900arbitrary search hit: http://www.vishay.com/leds/low-current/  funny how most of them are 1V8 irrespective of color
15:37.24*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
15:37.36*** join/#neo900 louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
15:39.01Joerg-Neo900well  the real threshold Vfwd is 1.62 to 1.74V for red over orange to yellow
15:39.14*** join/#neo900 chomwitt (~chomwitt@athedsl-31537.home.otenet.gr)
15:39.27Joerg-Neo900with a virtual ESR of ~25 Ohm
15:48.25Joerg-Neo900though we can adjust that very easily in prototypes, I'd suggest a series R of 1k
15:48.48Joerg-Neo900for 1V8 logical signals
15:49.05Joerg-Neo900that roughly equates a 0.1mA
15:58.27*** join/#neo900 SylvieLorxu (~TheLastPr@541B7AAC.cm-5-4b.dynamic.ziggo.nl)
16:37.52*** join/#neo900 xmn (~xman@user-0cdft6f.cable.mindspring.com)
17:10.01Joerg-Neo900ooh, and GND side of diodes please across one common 0R
17:35.51Joerg-Neo900unrelated: http://maemo.cloud-7.de/share-service/pitch03_2.png (stencil 0.3 pitch)
17:37.08Joerg-Neo900*cough* http://wstaw.org/m/2016/12/19/plasma-desktopJ17764.png
18:20.40*** join/#neo900 jonsger1 (~Thunderbi@5.255.80.126)
18:22.24*** join/#neo900 chomwitt (~chomwitt@athedsl-31537.home.otenet.gr)
18:24.44*** join/#neo900 jonsger1 (~Thunderbi@HSI-KBW-046-005-000-118.hsi8.kabel-badenwuerttemberg.de)
19:57.33*** join/#neo900 fling (~fling@fsf/member/fling)
20:56.17*** join/#neo900 louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
20:56.44*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
21:13.58*** join/#neo900 jonsger (~Thunderbi@HSI-KBW-046-005-019-111.hsi8.kabel-badenwuerttemberg.de)
21:42.53*** join/#neo900 Kabouik (~quassel@65.76.93.92.rev.sfr.net)
22:13.50*** join/#neo900 louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
22:14.46*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
22:33.33*** join/#neo900 qwazix (~qwazix@Maemo/community/ex-council/qwazix)
23:10.51*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
23:11.04*** join/#neo900 louis__ (~louisdk@static-5-103-130-65.seas-nve.net)
23:59.34*** join/#neo900 silviof (~silviof@unaffiliated/silviof)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.