**** BEGIN LOGGING AT Thu Apr 05 03:00:05 2018
Apr 05 13:16:02 <APic> ~flasher
Apr 05 13:16:04 <infobot> refer ~flashing; http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz (also .exe!), or http://www.chakra-project.org/ccr/packages.php?ID=5027 or generally http://www.google.com/search?q=maemo_flasher-3.5_2.5.2.2.tar.gz.   HARMattan(N9): https://aur.archlinux.org/packages/fl/flasher-harmattan/flasher-harmattan.tar.gz; list of filenames/md5sums: http://pastebin.com/sYKdNJSH, or http://galif.eu/nokia/
Apr 05 13:17:26 <APic> ~lf
Apr 05 13:17:27 <infobot> from memory, #maemo lazyflashing is http://wiki.maemo.org/Updating_the_tablet_firmware#The_Lazy_Approach
Apr 05 13:56:11 <APic> ~sb
Apr 05 13:56:12 <infobot> it has been said that scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB
Apr 05 19:17:25 <sicelo> not really a question for here - but, if i fork a repo on github, and the original repo changes, do those get reflected in my 'copy' of the repo? or i have to do something manual?
Apr 05 19:17:45 <sicelo> or they are like a snapshot of the state of the original at the time i did the fork?
Apr 05 19:20:17 <Wizzup> you can an exact clone with full history.
Apr 05 19:20:45 <KotCzarny> you will have to pull changes once you fork
Apr 05 19:21:40 <KotCzarny> that's why it's a fork and not some kind of magical ghost
Apr 05 19:21:59 <Wizzup> 'at the time'
Apr 05 19:22:07 <Wizzup> oh, maybe I misread the question
Apr 05 19:22:09 <Wizzup> :)
Apr 05 19:22:11 <Wizzup> bbiab
Apr 05 19:22:12 <KotCzarny> yup
Apr 05 19:22:13 <KotCzarny> :)
Apr 05 19:23:25 <sicelo> thanks. now to find that on Github web interface
Apr 05 19:23:44 <KotCzarny> look for 'merge'
Apr 05 19:23:46 <KotCzarny> or something
Apr 05 19:24:12 <KotCzarny> but i'm not git/github expert so i may point to wrong item
Apr 05 19:25:24 <sicelo> i'll look thanks. i already can see that changes in original repo haven't made their way into the fork :)
Apr 05 19:25:28 <Blooser> Hey!
Apr 05 19:25:31 <Blooser> I have a problem
Apr 05 19:25:40 <KotCzarny> everyone has problems
Apr 05 19:25:44 * sicelo is also a git nobody 
Apr 05 19:25:52 <Blooser> Sorry, no terminal at all requested - can't get input
Apr 05 19:25:52 <Blooser> gpg: Sorry, no terminal at all requested - can't get input
Apr 05 19:25:55 <Blooser> Look
Apr 05 19:26:00 <Blooser> error with gpg
Apr 05 19:26:07 <Blooser> Do you know how to repair it?
Apr 05 19:26:27 <KotCzarny> i dont
Apr 05 19:26:27 <Blooser> I wrote "gpg --full-generate-key"
Apr 05 19:26:27 <sicelo> Blooser: maemo?
Apr 05 19:28:02 <KotCzarny> hit'n'run problem solving?
Apr 05 19:28:05 <sicelo> heh
Apr 05 19:42:48 <DocScrutinizer05> sicelo: a fork is to avoid changes in original propagating into your fork, otherwise you'd branch instead of fork
Apr 05 19:43:11 <DocScrutinizer05> and even on branches you still need to merge
Apr 05 19:44:43 <Wizzup> that is not true for forks on github
Apr 05 19:44:57 <Wizzup> on github, people fork to be able to send back changes through merge requests on their own forks
Apr 05 19:45:10 <Wizzup> s/people fork/people usually fork/
Apr 05 19:45:10 <infobot> Wizzup meant: on github, people usually fork to be able to send back changes through merge requests on their own forks
Apr 05 19:45:46 <DocScrutinizer05> nfc about github, I hate it. I hate git as well but at least understand some basics since I done other VCS in my professional life
Apr 05 19:46:09 <KotCzarny> wizzup: how is merge different from pull request?
Apr 05 19:48:02 <Wizzup> DocScrutinizer05: his question was about github
Apr 05 19:48:13 <Wizzup> so it makes sense to answer his question in that context
Apr 05 19:48:27 <Wizzup> KotCzarny: sorry?
Apr 05 19:48:55 <KotCzarny> ahm, one might think about pull request as a reverse of the merge
Apr 05 19:49:52 <Wizzup> both are bidirectional. but a pull request is typically to the repo you've forked.
Apr 05 19:50:01 <Wizzup> they're essentially the same
Apr 05 19:56:38 <Maxdamantus> Well, a "pull request" in github is a request for someone else to merge two branches and update the target branch to be the result of that merge.
Apr 05 19:58:52 <Maxdamantus> That's at least what happens if you get github to actually perform the actions desired by the pull request (it just does a non-fast-forward merge) and updates the branch.
Apr 05 19:59:40 <Maxdamantus> You can always just treat the pull request as denotational though, so the owner of the target repository is not somehow obligated to do that.
Apr 05 20:00:00 <Maxdamantus> Could just fix the issue yourself and close the pull request.
Apr 05 20:00:15 <Maxdamantus> or cherry pick the commits instead, etc
Apr 05 20:12:29 <Maxdamantus> 07:23:44 < KotCzarny> look for 'merge'
Apr 05 20:12:42 <Maxdamantus> I was looking for that recently. I don't think it really exists.
Apr 05 20:13:06 <Maxdamantus> but you can create a pull request for your own repository with the source being in another repository.
Apr 05 20:13:39 <Maxdamantus> though when you get the site to do the merge, it will create an extra commit, since it always does a non-fast-forward merge.
Apr 05 20:14:06 <Maxdamantus> I just did that recently so I didn't have to push hundreds of megabytes of missing commits from my own internet connection.
Apr 05 20:14:37 <Maxdamantus> https://github.com/Maxdamantus/nixpkgs/pull/1
Apr 05 20:14:37 <sicelo> makes sense .. i can't find it, and am beginning to feel dumb
Apr 05 20:22:02 <Maxdamantus> Note though that you can just push the commits directly from your own local repository.
Apr 05 20:22:25 <Maxdamantus> git push my-github remotes/other-github/master:master
Apr 05 20:23:18 <Maxdamantus> (assuming your local repository has "my-github" as a remote for your own github repository and "other-github" as a remote for the source one)
Apr 05 20:23:33 <Maxdamantus> (you'll need to `git fetch other-github` to mak
Apr 05 20:23:53 <Maxdamantus> -e sure remotes/other-github/master is up-to-date)
Apr 05 20:31:18 <DocScrutinizer05> Wizzup: sorry, I didn't realize that
Apr 05 20:32:17 <DocScrutinizer05> Wizzup: I also wasn't aware github is such terrible mess that not even generic VCS rationale applies
Apr 05 20:32:51 <Wizzup> github can be used as regular git, it's just that their ui helps people who don't quite grok git use it in a different way
Apr 05 20:33:08 <Wizzup> but the term 'fork it' doesn't hold the same connotation as it does elsewhere
Apr 05 20:33:26 <Wizzup> github encourages people to fork and then do merge-back requests (pull requests)
Apr 05 20:33:36 <Wizzup> it's essentially decentralisation of auth on their centralised hosting
Apr 05 20:34:04 * DocScrutinizer05 is used to sending patch emails ;-)
Apr 05 20:34:54 <DocScrutinizer05> good hint that github's semantics differ in this aspect
Apr 05 20:36:00 <DocScrutinizer05> I'm pretty sure it already confused the hell outa me when users mentioned forhing though thexy did mean github-"fork"
Apr 06 02:12:01 <Oksana> How does auto-complete on Maemo work? Because I think that it would benefit from aspell or something similar, to understand prefixes and suffixes easier. Instead of thinking that "dog" and "dogs" are different words?
**** ENDING LOGGING AT Fri Apr 06 03:00:00 2018