@Tim
No need to be sorry mate :)
It is particularly easy to post binaries to GitHub but that is entirely up
to the repo owner. I would do the following:
Check tiennou/blacktree-alchemy Downloads tab and look at the date of the
last item posted.
Check andreberg/blacktree-alchemy Downloads tab look at the date of the last
item posted.
Download whichever is more recent. Probably goes without saying but remember
to always backup your data first.
Details are in the README.markdown about that.
Now this is important:
Development will happen distributed as this is the nature of Git. Etiennes
repository (tiennou/blacktree-alchemy) will be the main one from which all
other developers will download a repo copy ("fork" in git speak) and do
their changes on their own copy. When satisfied with their changes
developers will ask Etienne to pull from their fork which incorporates the
new changes into Etienne's repository.
Etiennes repository should always be (in the end) the one which has all
changes so this should be your first address to check. It can of course
happen that my fork or any other devs fork appears to be newer because I
haven't asked Etienne to pull from me yet. That's why I gave the order
above.
NOTE: This also means that effective immediatly
github.com/andreberg/Quicksilver-B5X is obsolete and I may delete this repo
in the future.
As said I will continue my development on my fork of Etienne's repo (where
he already was so kind to do the work I should have done and incorporated my
changes of github.com/andreberg/Quicksilver-B5X) at
github.com/andreberg/blacktree-alchemy.
This also means that issues should now be posted at
github.com/tiennou/blacktree-alchemy. I will post the issues I have recieved
at github.com/andreberg/Quicksilver-B5X over at Etienne's repo if the Issue
owners don't do it themselves.
I know this is a bit confusing but we will get behind this :) Took me quite
a while to figure out Git too. But once your on top of things it really is
so much better for exactly our kind of project.
André
2009/11/10 Tim <[email protected]>
> Yep - should have said, so very sorry. I removed the icon from the dock
> (dragged it off the dock) and then went into the QS prefs pane (now that it
> shows up in your 3838 build, André) where I noticed that the option to show
> it in the dock was unchecked. Checking it returned the normal / expected
> behaviour.
>
> On an entirely different tack, can we expect new builds of the QS.app (the
> app not the source code) to be made available on the github from time to
> time as things progress? If so, at which location - 'andreberg' or
> 'tiennou'? And how would notification of such builds be made?
>
> Finally (for the moment at least) - I'd like to express my sincere and
> heartfelt thanks to everyone who's going to such efforts to make QS
> compatible with SL. It's an indispensable app. to me (I much prefer it to
> LaunchBar).
>
> Tim.
>
>
