<Kaik541>
supercurio: in fact I had to convince several people to set a system in place so that we COULD do that override even if it changed the model/product name of the device would still output the correct zip
<nebkat>
supercurio: we have hundreds of devices, respecting original codename is not our priority
<Kaik541>
it was the whole point of the ro.cm.product
<supercurio>
nebkat, I noticed it was not a priority ^^
<nebkat>
supercurio: does market filtering not use the fingerprint?
<supercurio>
nebkat, but I don't see the benefit of keeping errors
<nebkat>
rather than the ro.product.model
<nebkat>
supercurio: what?
<supercurio>
nebkat, from the list appearing it looks like Build.DEVICE
<supercurio>
but I can't tell for sure
<nebkat>
mmh
<nebkat>
wait
<supercurio>
see you have names like: espressowifi
fel-x has quit [Quit: Leaving.]
<supercurio>
galaxys2
<nebkat>
supercurio: you want ro.build.product to be m0
<supercurio>
d2can
<Kaik541>
supercurio: we do not use the espressowifi
<nebkat>
and ro.cm.product to be i9300?
<Kaik541>
supercurio: it goes by the model number
<Kaik541>
supercurio: the name of the zip is not always the name of the model
<Kaik541>
supercurio: blame AOKP for espressowifi
<supercurio>
Kaik541, yes but Google Play knows picasso.
<supercurio>
oops
<supercurio>
I meant espressowifi
<supercurio>
I don't blame anything
<supercurio>
I'm trying to report how Google Play works ;)
<Kaik541>
supercurio: the device tree name and zip name don't always line up with what the model reports as
<Kaik541>
that's just how we name the releases
<nebkat>
supercurio: set ro.build.product to m0
<nebkat>
supercurio: then test it
<Kaik541>
supercurio: for instance, the Samsung Galaxy S zip is released as "galaxysmtd" but shows up in the market and is identified as GT-I9000
<Kaik541>
supercurio: also the d2 devices *are* the names of the SGS3 devices in USA
<Kaik541>
so those are definitely correct
<supercurio>
from the Galaxy S III SIM unlock tool play store backend
<Kaik541>
supercurio: galaxys2 is a deprecated name that we fixed a long time ago
<Kaik541>
supercurio: blame users who don't update their shit
<supercurio>
Kaik541, its recorded forever in Google Play history
<Kaik541>
supercurio: and my point is we moved away from it specifically to fix that problem
<Kaik541>
so we've already "fixed" that, but you're still going on about it
<supercurio>
anyway
<supercurio>
it doesn't change why I came here
<supercurio>
to report an error in build.prop ^^
<Kaik541>
supercurio: then submit a change to gerrit
<Kaik541>
it's not hard
<supercurio>
invalid values set, not a political statement :p
<Kaik541>
if you don't like the way something's being done in CM, it's open source and can be change, feel free to do it
<nebkat>
+1
<supercurio>
I really don't understand the reaction guys
<supercurio>
what's wrong with my error report?
<Kaik541>
supercurio: our point is that you consistently come in to complain about some issue with CM, and while we admit that CM isn't perfect, instead of just COMPLAINING about it, offer a solution or a way to fix it
<supercurio>
why does it generate a debate since 20minutes
<supercurio>
really, I don't understand
<supercurio>
Kaik541, I'm not complaining
<supercurio>
Kaik541, I report an issue
<Kaik541>
you "blame" us for having an inconsistent market filter
<supercurio>
Kaik541, people do what they want with it
<Kaik541>
supercurio: ok then we're most likely going to promptly ignore it then
<Kaik541>
supercurio: if it's an issue that affects you directly, please, feel free to provide a fix
<supercurio>
Kaik541, then nebkat tell me "<nebkat> supercurio: because we dont care about third party apps"
<supercurio>
lol
<Kaik541>
that's the whole point of a collaborative open source effort
<supercurio>
sorry, it was a troll and I fall into it, guilty ^^
<Kaik541>
no it's not a troll, honestly, if you choose to create a blacklist, then it's up to you to keep it up to date
<supercurio>
Kaik541, come on
<nebkat>
supercurio: what I was trying to say is, we will never change our internal development process due to a third party app
<nebkat>
referring to your last complaint...
<supercurio>
ok
<supercurio>
I'm loosing my time here
<supercurio>
'later
<Kaik541>
supercurio: you have an issue with the way CM is doing something, an issue that already has a system in place that can fix it, but instead of offering up the fix so that it stops messing with your incompatibility issues... you just tell us "HEY IT'S BROKEN"
<Kaik541>
supercurio: how is that any better than users on forums going "IT DOESN'T WORK" and not providing any logs?
<supercurio>
now, you'll be nice publishing a blog post or something for developers
<nebkat>
supercurio: what?
<Kaik541>
what?
<nebkat>
ok let me put it to you simply
<supercurio>
"How app developers are supposed to detect which device they're running on under non-standard CyanogenMod OS"
<nebkat>
I, and pretty much all of cm, dont give a shit about any app
IamSachin has joined #teamhacksung
<nebkat>
if you see something wrong
<nebkat>
fix it yourself
<supercurio>
I recall very clearly cyanogen himself saying it was an absolute priority to not break applications compatibility
<supercurio>
if you really think otherwise, I can paste you the message if you want
<nebkat>
ok, but cant you see what im saying?
<nebkat>
if you see something wrong, fix it
<supercurio>
nebkat,
<nebkat>
dont come here saying "please fix this I need it for my app"
<supercurio>
I'm working on an app, people expect an update fast
<supercurio>
nebkat, I come on IRC
<supercurio>
say one thing
paulk-desktop has quit [Ping timeout: 248 seconds]
<nebkat>
and we dont care about your apps
<Kaik541>
supercurio: then update your app, don't blame CM
<nebkat>
just saying
<supercurio>
I'm not forcing you to do anything
<supercurio>
I'm just talking
<nebkat>
I know
<supercurio>
you know
<supercurio>
expressing myself
<Kaik541>
supercurio: but you're complaining and you're putting literally *all* of the blame on us
<supercurio>
"oh, and error here"
<Kaik541>
supercurio: the problem is you are telling us "this is an issue, now you guys should go fix it, bye now"
<supercurio>
I could tweet it, I could blog it, I could write it on Google
<supercurio>
instead I tell what I found on IRC
<Kaik541>
supercurio: instead of doing that, how about *you* offer the fix for *your* app
<supercurio>
am I so important everything I say sound like a request?
<nebkat>
ok
<nebkat>
thank you for your report
<supercurio>
that people feel obliged to comply to?
<Kaik541>
I've never heard a single user complain about your app not working while on CM
<supercurio>
okay
<nebkat>
we will consider it
<supercurio>
thank you
<nebkat>
if you want a fix, do it your self
<nebkat>
yourself*
<nebkat>
I can't guarantee anything
<Kaik541>
supercurio: no, but the fact that this is consistent behavior we see from you where you regularly drop by to tell us that we're doing something wrong while simultaneously offering no solution is annoying
JieeHD is now known as JieeHD|Offline
<supercurio>
Kaik541, its 2 lines in a text file
<stickyboy>
Stock ROM identifies to market as m0. Why doesn't CM?
<supercurio>
Kaik541, I don't know gerrit
<supercurio>
Kaik541, I don't know the process to submit a patch
<Kaik541>
stickyboy: I agree that that's bad, it's the whole reason the ro.cm.product exists and should be used but codeworkx messed it up
<Kaik541>
supercurio: that's why we have a wiki
<supercurio>
Kaik541, I don't know in which repository it is
<supercurio>
Kaik541, I don't know who to contact to gain access
<Kaik541>
this is specifically written for people like you who find an issue they want resolved
<Kaik541>
go ahead, resolve it
<supercurio>
It's also not just two lines
<supercurio>
its 2 lines worth discussing
<Kaik541>
how is it worth discussing?
<supercurio>
as it's used as market filter and also by developers
<Kaik541>
there is already a system in place to do exactly what you're talking about
<supercurio>
like me
<nebkat>
supercurio: you probably dont understand our system
<nebkat>
there is no "discussing"
<nebkat>
if you see something wrong
<nebkat>
go fix it
<Kaik541>
but instead of just using it and offering the fix, you're giving us excuses for why you can't
<nebkat>
send a patch
<supercurio>
so instead of coming here for each device "oops, it's the worng value again"
<nebkat>
we will merge it
<supercurio>
I try to understand why those 1 or 2 lines are constistently invalid in CM
<Kaik541>
supercurio: because clearly we hate you
<Kaik541>
supercurio: just to make your life harder
<supercurio>
Kaik541, not helping
<Kaik541>
supercurio: you say it like it's an accusation, so yes I'm going to respond sarcastically
<Kaik541>
as though we're somehow intentionally breaking stuff
<supercurio>
Kaik541, of course no!
<supercurio>
Kaik541, but I notice people choosing values in build.prop are not aware that it break stuff
<supercurio>
Kaik541, so they don't pay attention to it
<Kaik541>
supercurio: do you forget that CM doesn't even include the google applications? so really "market and app compatibility" is pretty low on our list of priorities (though we do try not to break it)
<nebkat>
good point
<Kaik541>
supercurio: then fix it, you have the source and you have the changes
<supercurio>
Kaik541, values set are probably chosen by a script
<supercurio>
or something like that, I don't know how it works
<nebkat>
no
<supercurio>
but as CM developers are not neccesarily application developers as well
<supercurio>
now, you can understand that instead of sending a patch for each new device
<Kaik541>
see captivate responds correctly, i9300 doesn't
<Kaik541>
compare the two, find what's different, fix it
<supercurio>
I try to understand the source of the issue
<supercurio>
and have it not re-appearing later
<nebkat>
<supercurio> now, you can understand that instead of sending a patch for each new device
<supercurio>
why I come here to talk instead
<nebkat>
yes, you should send a patch for everything
<nebkat>
just how one of us would have to do anyway
<Kaik541>
supercurio: see that line in the first link I sent you?
<Kaik541>
PRODUCT_DEVICE := i9300
<Kaik541>
change that to PRODUCT_DEVICE := m0
<Kaik541>
done and done
<Kaik541>
submit the change
<supercurio>
Kaik541, thanks for the links
lolwat has quit [Read error: Connection reset by peer]
<supercurio>
now
<nebkat>
might be some more dependencies
<supercurio>
I understand there are some values intentionally different
<Kaik541>
nebkat: nope, the system was put in place to make it work exactly like that
<supercurio>
like PRODUCT_NAME := cm_i9300
<Kaik541>
nebkat: since captivatemtd wasn't working
<nebkat>
Kaik541: ah
<nebkat>
Kaik541: thought we might have some makefile ifs
<supercurio>
do you know which one is intentionally modified compared to Samsung build.prop maybeN
<supercurio>
?
<Kaik541>
supercurio: there is a process along the way that will change m0 to the "CM approved name" without changing the important bits
<supercurio>
or I should ask to codeworkx instead as he worked on that
<Kaik541>
supercurio: I don't think it's ever intentionally modified to be different, just overlooked and forgotten and mistakes are made
<Kaik541>
supercurio: the whole point of the collaborative review process in an open-source project is specifically so someone else can catch our mistakes and provide the solution
<nebkat>
yeah
<nebkat>
we would never intentionally change it
<Kaik541>
supercurio: I have given you the tools to provide the solution to us and instructions on how to use them, instead of talking about it with codeworkx where he might just ignore you, offer the solution on gerrit and solve the issue that's bothering you
<nebkat>
end of story
<nebkat>
fix it if you want it fixed
<supercurio>
PRODUCT_NAME := cm_captivatemtd << it's the one appearing in build.prop eventually or it's processed ?
<Kaik541>
supercurio: that becomes ro.cm.product iirc
Baskey has left #teamhacksung ["If"]
<supercurio>
ok
<Kaik541>
supercurio: but if you look, those all get overriden later in the build process
<Kaik541>
nebkat: let him do it so he can fix it where he needs to and he'll learn how to fix other things later if need be
<nebkat>
ok
<supercurio>
nebkat, lol wait I'm trying to find my way in gerrit (failing so far^)
<nebkat>
good luck ;)
<nebkat>
if you need I can give you step by step tutorial
<Kaik541>
supercurio: I'll brb if you need any help figuring stuff out, need a cigarette
<supercurio>
lol all I find related is "report bug" but it's for gerrit not CM :p
<nebkat>
supercurio: you arent reporting a bug, you are making a patch
<Kaik541>
supercurio: make sure you follow the instructions about syncing the source
<nebkat>
supercurio: btw, in s3 sim unlock app, if it says "sim lock: inactive" it means I am already unlocked?
<nebkat>
Kaik541: lol
<supercurio>
nebkat, yep
<nebkat>
supercurio: do you use linux?
<supercurio>
nebkat, yes
<nebkat>
do you have cm synced
<nebkat>
cm source
<supercurio>
for .. 9 years as desktop something like that
<supercurio>
no I made some room on my SSD and deleted it recently ^^
<Kaik541>
nebkat: you should submit the patch to jellybean and let supercurio do it for ICS
<nebkat>
:)
KalimAz is now known as KalimAz|Away
<supercurio>
reading the docs now
<supercurio>
I can't find how to create a new patch or issue or something
<supercurio>
it seems consultation only
<Espenfjo>
I guess you need to sync sources
<Espenfjo>
Since we are redoing the device trees for JB anyways, we should do it right imho. Altough I have no idea how all of these naming stuff works, yet.
<nebkat>
Espenfjo: we are?
Yoshimo has quit [Ping timeout: 264 seconds]
<Espenfjo>
we are
<Espenfjo>
galaxys2 -> i9100 && galaxys2-common
<Espenfjo>
common-thingie used by most exynos4 devices
<supercurio>
argh sorry guys I have to leave and then i'll go back to what I was doing (Voodoo Sound jelly bean Nexus S update)
<supercurio>
sorry can't spend several hours of setup for 2 lines today
<nebkat>
Kaik541: damn I was just pushing one myself
<Kaik541>
nebkat: needed to fix cm.dependencies anyway :P
<supercurio>
Kaik541, nebkat btw thanks for the explanation
<nebkat>
Kaik541: err revert to patchset 4?
<supercurio>
Kaik541, nebkat now I understand why it's so easy to have different values in the generated build.prop compared to manufacturer one
<Kaik541>
supercurio: yes, I had a long discussion with pawitp and arcee a while ago about fixing it (since it directly affected what captivate users had access to)
<Entropy512>
as to fixing cm.dependencies, shouldn't that be in a separate patch?
<supercurio>
hey Entropy512
<Entropy512>
samsung naming conventions make my head hurt
<nebkat>
Entropy512: yep
<Entropy512>
worst was c1 getting renamed to u1
makimac has joined #teamhacksung
<supercurio>
Entropy512, after a firmware update?
<Kaik541>
supercurio: GB to ICS
<supercurio>
ew ugly
<Entropy512>
yeah. Galaxy S2 was c1 in GB
<Entropy512>
u1 in ICS
<supercurio>
yes in this case the build process (and distribution) need to depend as little as possible on those values
<Kaik541>
nebkat: I'm fixing commit
<Entropy512>
oh yeah and I found out
<nebkat>
Kaik541: tnx
<Entropy512>
both N7000 and I717 are called "q1"
<Entropy512>
despite being TOTALLY DIFFERENT DEVICES INSIDE
<supercurio>
indeed
<supercurio>
Entropy512, build.device ?
<Entropy512>
not sure, I'm mainly thinking of the internal references in the source code
<Entropy512>
being primarily a kernel guy I mainly pay attention to those. :P
<supercurio>
I tend to fail to indentify which one of "product" or "device" is used for a family and for a specific variant
<supercurio>
identify
<supercurio>
google use constant "product" and varying "device"
<Entropy512>
samsung's naming conventions lead to pain and suffering
<Entropy512>
yesterday's meeting was productive, although I really thing the current situation is no-win for all involved, but at least it sets the stage for better cooperation going forward
pier|afk is now known as pier
<Entropy512>
turns out the eMMC repair process has a significant (>50% in the experiences of the engineer that was trying to implement it) chance of leaving a 100% toasted chip. :(
<supercurio>
Entropy512, makes me sad to read about no-win :(
<Kaik541>
supercurio: you will only be interested in the cm.mk changes
<stickyboy>
Yikes...
<supercurio>
Kaik541, nebkat congratulation guys, it's a HUGE MESS!
<supercurio>
;)
<Kaik541>
supercurio: blame nebkat for not responding xD
<supercurio>
hehe for 1 line
<Kaik541>
so I fixed his change while he reverted it
<supercurio>
I clearly underestimated the challenge behind ;)
<Kaik541>
supercurio: meh, the single line was easy, I was just also fixing other stuff while I saw it was broken (I don't build for i9300 ever so I hadn't noticed it)
<Espenfjo>
Entropy512: So they did infact admit they are having eMMC issues?
<Kaik541>
Espenfjo: they admitted that a long time ago iirc
<Entropy512>
yeah, that's been admitted for a long time
<Entropy512>
however I think we discovered some serious internal communications disconnects though
<supercurio>
Kaik541, yeah of course, extra care must be taken in this case using automatic generation
<Entropy512>
some of their engineers were telling the team I was working with that certain things were enabled that CLEARLY are not
<Kaik541>
supercurio: codeworkx is usually the one making the repositories so he misses out on what users are doing wrong sometimes
<Kaik541>
and by "doing wrong" I mean "following the instructions, but the device tree didn't get updated"
<Entropy512>
for example, it was claimed that MMC_CAP_ERASE being missing from I9100 Update4 source code was a mistake and all shipped binaries had it enabled
<supercurio>
Kaik541, yep
<Kaik541>
supercurio: our biggest problem with that is always the extract-files.sh script we have for pulling blobs, none of the maintainers use it and we're constantly updating or changing them so sometimes that script gets overlooked in the process
<Entropy512>
but we know from behavior that MMC_CAP_ERASE is NOT in any release prior to XWLPM/XXLQ5
<Entropy512>
and also Update5 and Update6 still don't have it
<Entropy512>
I think there was a miscommunication - someone saw that it was enabled in sdhci.c
<supercurio>
Kaik541, is cm.mk generated from extract-files.sh ?
<Entropy512>
and didn't realize mshci.c is what matters
<Kaik541>
supercurio: no
<Espenfjo>
:/
<Entropy512>
also one of their engineers is adamant that removing MMC_CAP_ERASE will kill performance because it's needed for discard
<Kaik541>
supercurio: cm.mk is something we make for build purposes
<supercurio>
ok
<Entropy512>
but as we all noticed - no released device I am aware of uses the "discard" mount option
<stickyboy>
Entropy512: Yikes, Catch 22...
<supercurio>
argh have to leave, see you guys and thanks for the help: Entropy512 will read the log with a lot of interest
<Entropy512>
i'm kinda taking a break for today from that while H flies home
<Entropy512>
gonna fix up infuse camera I think
IamSachin has joined #teamhacksung
IamSachin has quit [Client Quit]
<Kaik541>
Entropy512: make every infuse owners dream come true, official support with Jellybean
<Kaik541>
skip straight from stock GB to JB <3
<Entropy512>
As to submitting official - not sure. It's frustrating that gloryhounds who want to be able to say they are first are doing JB work when ICS still has serious issues
Kaik541 has quit [Quit: Leaving]
<Entropy512>
I'm wondering if I should do the MTD switchover before going official
<stickyboy>
Entropy512: Speaking of official, you saw ohanar and my Gerrit for P6xx0?
<stickyboy>
:P
<Entropy512>
yeah - why'd you eventually switch to a different kernel instead of pulling in fixes?
<Entropy512>
too many deltas?
<stickyboy>
ohanar was the one who did it.
<stickyboy>
But it immediately fixed problems we were having with graphics glitches, as well as i815 (p8lte).
<stickyboy>
And there were some other issues, too. Can't remember.
<Entropy512>
ah
Yoshimo has quit [Quit: Yoshimo]
<stickyboy>
The current kernel is based on Gt-I9300, P6200, and P6800.
<stickyboy>
Wifi works 5/10 now. 100% if we use Samsung's wpa_supplicant.
<stickyboy>
(err, kernel is based on ICS kernel drops for those devices)
KalimAz|Away is now known as KalimAz
<Entropy512>
I'm thinking of maybe eventually seeing if we can move I9100, I777, and N7000 to the I9300 kernel sources
<Entropy512>
because newer I9100 and N7000 releases are closer to I9300
pier is now known as pier|afk
<stickyboy>
Entropy512: It would be nice to be on one kernel again :P
<Entropy512>
freaking hell... jt forked the entire aries-common repo for just one patch
<Entropy512>
which should have been gerrited anyway because it's a good thing to have
IamSachin has joined #teamhacksung
<IamSachin>
Wassup doods
pier|afk is now known as pier
<supercurio>
Entropy512, I understand
<supercurio>
Entropy512, did Samsung people thanked or rewarded you for your effort in any way?
<Entropy512>
yeah they thanked me for my support and for meeting with them
<Entropy512>
the team that was there was great to work with
<Entropy512>
one thing I need to do is provide some tips on how to implement a kernel patch in a manner that lets someone verify that it's there
<supercurio>
Entropy512, and do you feel the thank was a good balance with you effort this time?
<Entropy512>
yeah I think so
<supercurio>
Entropy512, ok so its alright ;)
<Entropy512>
I think that we're not going to get much of a resolution for people who already got nailed, but after talking with them there is no real technical solution for it
<supercurio>
Entropy512, I was concerned about the reciprocity you know
<Entropy512>
but at least we can catch shit like this earlier
<Entropy512>
I got some useful information (some of which I can't share)
<supercurio>
Entropy512, to be sure they don't assume they're big so they just deserve evetything
<Entropy512>
well management may still think that...
<Entropy512>
the local team was great
<supercurio>
Entropy512, I compare with the week I spend with Wolfson at Edimburg
<supercurio>
Entropy512, same, I was not paid for it (except they paid the travel, hotel, even food)
<Entropy512>
Yeah, they paid for meals while I was around. :)
<supercurio>
Entropy512, but I learned a lot, was even trained on their Audio Precision tools in the lab so it was balanced ;)
<supercurio>
hehe
<Entropy512>
in my case it wasn't a visit to corporate HQ - so very different
<supercurio>
yup
<supercurio>
out of curiosity did they offered you a job?
<supercurio>
you may not answer to my question eh ;)
<stickyboy>
Entropy512: Did you take time off work for this? Or just something like lunch?
<Entropy512>
there was conversation I think sort of probing that, although without them saying that I already kind of said that I don't think I'd want to do this for a living during the conversation
makimac has quit [Quit: ChatZilla 0.9.88.2-rdmsoft [XULRunner 12.0/20120420145725]]
<Entropy512>
stickyboy: was Friday evening and Saturday
<supercurio>
Entropy512, yes
<Entropy512>
I feel kind of sorry for them, they were jetlagged so the entire time we met Sat is a time they'd normally be asleep. :)
<supercurio>
lol right
<supercurio>
and H was even 2 times in a row jetlagged
<supercurio>
didn't had the time to recover from the first one.. and again :D
<Entropy512>
heh... well she might have had time to recover from last week, other than it sounds like she's been working wacky hours
<Entropy512>
they prolly would've been better off not flying into JFK though
<supercurio>
do you think this kind of collaboration is new or
<supercurio>
it happened already in Windows Mobile days
<Entropy512>
new
<Entropy512>
H said it's the first time she's met with anyone from the community face-to-face
<supercurio>
I'm asking because Chainfire told me he had close contacts with manufacturer in WM days
<supercurio>
yep!
<supercurio>
thats amazing
<stickyboy>
"H"?
IamSachin has quit [Remote host closed the connection]
<Entropy512>
we don't want to give out our contact's name in a public channel lest she get uberspammed
<Entropy512>
:)
<stickyboy>
Entropy512: No problem. Thought it might be that.
<supercurio>
stickyboy, codename for a Samsung contact, you would be be elimitated if we tell more ^
<supercurio>
hehe
* stickyboy
reveals that he is H. *dun dun dun*
<Entropy512>
we know H is a she. :P
stickyboy is now known as stickygal
<supercurio>
and stickyboy realize he is a women :D
<supercurio>
lol
<Entropy512>
lol
stickygal is now known as stickyboy
<stickyboy>
:D
<Entropy512>
inflight wifi? :P
<stickyboy>
hahaha
<supercurio>
Entropy512, its new so there's no need to define specific rules I guess
<stickyboy>
Check my IP, I'm "flying" over Kenya.
<supercurio>
Entropy512, but if it becomes common maybe it might be useful to define certains terms or contracts something like that
<Entropy512>
that reminds me I need to reserve flights for BBQ
<Entropy512>
she's getting heavy pressure to attend from multiple places. :P
<supercurio>
yep, adding to the pressure :p
<supercurio>
eh BTW, who from the channel will be there at the BBQ?
<supercurio>
nebkat, will you be at the BBQ? I hope I'll be able to come annoy you with stupid erros ! :)
<stickyboy>
supercurio: Ah, are you going?
<supercurio>
yeah! at last :)
<stickyboy>
Wow, cool. All the way from France :)
<supercurio>
I shall talk about stuff too (but quickly)
Doron` has joined #teamhacksung
<supercurio>
and I can't wait to hear Entropy512, as I like reading him already
<stickyboy>
How does BBQ work, are there talks?
<stickyboy>
I'm going to a wedding in Alsace next weekend. I think it's too far from supercurio though. :)
<Entropy512>
afk a bit
<supercurio>
'later Entropy512
<supercurio>
stickyboy, sorry I don't remind where you're from,
doron has quit [Ping timeout: 245 seconds]
<stickyboy>
supercurio: I live in Kenya. :)
<supercurio>
oh right!
<supercurio>
yeah that's quite a trip to come to Alsace
<stickyboy>
But I'll be in Europe next week to for work and other stuff.
<supercurio>
unfortunately its kinda as far as it gets in France from where I live
Doron` is now known as doron
doron has quit [Changing host]
doron has joined #teamhacksung
<stickyboy>
I hear they have nice pastries in Alsace.
<stickyboy>
I only eat beans and spinache in Kenya. haha.
<supercurio>
yes even if Alsace is also known for delicatessen
<supercurio>
and sauerkraut
<stickyboy>
Hehe, not my favorite.
<stickyboy>
Actually, the French lady is marrying a German.
<supercurio>
Alsace is a bit like Germany but in France
<stickyboy>
I guess that region has been German before hehe
<stickyboy>
Yah
<supercurio>
yes it has been sometimes german, sometimes french (and source of conflicts)
<stickyboy>
I will only be there for 3 days :\
<stickyboy>
My girlfriend is studying her PhD in Basel, so I'll be there as well.
<supercurio>
I'm sure those 3 days will be far too short
<stickyboy>
I'm taking a train from Basel, so at least I'll see something :)
<nebkat>
supercurio: nah, not going
<supercurio>
stickyboy, you plan to make some sleep reserves and not sleep during the whole 3 days ? :p
<nebkat>
on holidays at the time and quite far away
<supercurio>
nebkat, you went there already another year?
<nebkat>
supercurio: no
<stickyboy>
supercurio: I will stay up all night eating pastries and drinking coffee. :)
<nebkat>
supercurio: haven't ever been there, and probably never will be lol
<supercurio>
nebkat, I assumed you're from the US but I might be totally wrong!
<nebkat>
supercurio: im from serbia but I live in ireland
<supercurio>
nebkat, oh right its quite far ;)
<stickyboy>
He said "holidays"... that was my first clue. We Americans don't say that. :P
<supercurio>
stickyboy, hehe. Yes or spend time with her I hope ^