a beer keg that would behave like the milestone 2.0.0 issue list. 

to help drink it! 

but I'm already 3 merges in so I'd like to think I have kind of "pulled my weight" ;)

I do want to contibute more at some later point (or if there's problems with the linux packages). 

Didn't make the connection there. You're excused ;-) 

SleepwalkR, I'm not sure if you see comments on closed issues on github, so I'll just post this here. Sorry if this is not the right place.

I'm still having problems with aligning textures on different brushes at once. As of a46b9f2, I can now separately fix each brush's texture, but I still cannot select multiple brushes and edit their angles/offsets/scales jointly. Pretty sure this used to be possible in an earlier build. 

 

 

I don't know how to reopen an issue once it's been closed ... or do you mean open a new issue? 

But either way you can still comment and I will see it. 

 

Probably a stupid question, but is it possible to have two or more different builds on one machine at the same time? So if something is broken in the latest build, you can keep using the latest-but-one build and then update the other one when an even newer build gets released.

Err, I am explaining this really badly, but maybe you know what I mean?

(I strongly suspect that's one of the reasons people use github, but I really struggle to understand how git/github actually works. The online documentation seems to assume a fair amount of prior coding knowledge, and I just get lost when I try to decipher it). 

You could just backup the binaries. Most of the changes happen in the executable so if you got that from before and run that it should work.

Also you are right since git is a decentralizid versioning system you have all of the version history on your computer too.

In the command line type

$ git log

and you can see the recent commits. Each commit has a sha1 hash identifier. (cryptic string)

� git checkout 43f2298 (first few chars of that string)

Will set you directory to how it was at that time. Then just rebuild.

afterwards

$ git checkout develop

to go back to the most recent version 

That helps a lot, although there are a few things I still don't quite get. Need to read through this a few times though before I ask more stupid questions. 

How does that work again? Has it changed over the last few builds? I can't figure it out... 

 

 

Where do I see how many brushes I have in my map? (I feel like I used to know this, but now I can't figure it out). 

 

Will it be possible in a later build?

And another question: is it possible to merge groups, brushes and entities into pre-existing groups (without creating nested groups in the process)? If not, would it be worth requesting this functionality on github? 

... or for that matter, removing brushes and entities from groups (not deleting them, just ungrouping them while retaining the rest of the group) would also be amazingly useful.

But maybe all of that is already possible? 

moving stuff in and out of groups is possible, but currently broken. I'll add a bug report for this. 

 

They're in the repository. 

Meaning I just need to update to the latest build?

Wow, you're fast. :) Thank you! 

That's fantastic; just what I needed. :) Thanks again!