<gzg>civodul: You actually caught me right before I was about to take a nap -- fyi though, later I plan on posting about kbd.scm to the guix-devel list... since the other didn't ever get to bug-guix. :^P
<a_e>Yes. But in my own branches there are usually just a few commits (like one for a new package) that I wish to put on top of master.
<mark_weaver>I don't think that switching back and forth between the branches is optimal, though.
<a_e>We merge between core-updates and master, which looks reasonable.
<mark_weaver>I think perhaps "git rebase origin/master" is a simpler and more efficient way to do what a_e is talking about.
<mark_weaver>it's possible that a "git fetch" might be needed somewhere, I'm not sure.
<a_e>mark_weaver: Probably so. I suppose one could also work more on branches without checking them out.
<mark_weaver>I use the "git-new-workdir" script (which comes with git) extensively, which allows me to have multiple working directories, each on a different branch, but sharing the same underlying git repo.
<mark_weaver>I can have my private branch in one workdir, and then if I realize I want to make a change to stable-2.0, I can do that in a separate directory without disturbing my private work-in-progress.
<Steap>a_e: having to run "make clean" is a bit annoying :/
<mark_weaver>a_e: the git-new-workdir script is in git-*/contrib/workdir/
<civodul>not sure if we could have a quick workaround for Guile <= 2.0.9
<mark_weaver>civodul: I'm not sure if you read the beginning of this discussion, but zacts' college has a transparent web proxy that munges the "Last-Modified" headers to end with "UTC" instead of "GMT", in violation of RFC 2616.
<mark_weaver>the third one is quite different from the other two. it's not so much about "normal" scheme programming, but about a logic programming system called "mini kanren" that can be very easily built on top of scheme.