Arc Forumnew | comments | leaders | submitlogin
Moved my hacks to hacks.catdancer.ws (catdancer.ws)
5 points by CatDancer 4558 days ago | 5 comments


1 point by shader 4555 days ago | link

How do you organize your hacks in git? I'm working on several libraries, and I'm running into the issue that I want them in separate version control so that I can push them to github separately, if need be, and not pollute Anarki until I'm finished. At the same time, I need them in the arc lib directory for using. How did you solve this one? Just keep them in separate folders near your arc installation and do (load "../blah/lib.arc")?

-----

1 point by CatDancer 4555 days ago | link

One approach is to create a clean patch that doesn't have any of your private development history in it. See Linus Torvalds comments: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/...

So if you want your library foo.arc to land in Anarki in the lib directory, create a patch to Anarki that adds foo.arc to the lib directory in a single commit.

One way to do this is to have one branch that tracks Anarki, and then a separate branch for your own development. You can merge new Anarki commits into your private development branch, but avoid ever merging from your development branch back into your Anarki tracking branch directly. Then in your private development branch you can have a messy development history (create foo, change bar, change foo, do something else, then change foo again), but only have add clean commits to your Anarki tracking branch that you push to Anarki ("create foo" or "update foo").

-----

2 points by shader 4558 days ago | link

Mind if I ask why you moved them away from github, and why you didn't move all of them?

-----

3 points by CatDancer 4558 days ago | link

I was using github's cool Github Page feature, where you can push a git repository to them, and they'll automatically create a web site out of it. The thing is, after you do the push, it goes into a queue, and some random time later depending on how busy github is the push will be processed to actually publish the changes. I found it was breaking my flow; the first thing I want to do when I publish something or write some instructions "go here and get this" is to try it and make sure that it's actually working. Nothing against github, it just wasn't a good fit for my particular work pattern.

I'm also slowly automating the hack documentation, so while naturally I do want to keep the source under version control it's just an extra step to have the generated HTML also in a git repository.

And I have aspirations of someday making this into a web app where anyone can publish their hacks, so it couldn't stay on github forever anyway.

I plan to still push the hacks to github, that way if my personal server goes down people won't be stuck waiting for me to fix it.

why you didn't move all of them

oh, I just don't have everything moved over yet.

-----

1 point by CatDancer 4557 days ago | link

And some were bug fixes for arc2 which have been fixed in arc3.

-----