You would need to give phantomotap, Sebastiani and other contributors (if any) write access to your repository after they register with Bitbucket. Alternatively, they would send you changegroup files by using hg bundle which you would then apply to your repository (using hg unbundle or hg pull, apparently), but that would not be making full use of Bitbucket, methinks.Originally Posted by matsp
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Makes sense. (I think the mercurial term is changeset, but same thing).
When I worked on Xen, we used hg export and send the resulting text as an e-mail to xen-devel mailing list, but between three or so people, I think that would be a bit overkill (since the whole idea of version control is that you can go back to an old version if someone broke it completely).
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
The Mercurial term is changegroup, i.e., a collection of changesets. Bazaar would call the rough equivalent a merge directive, if I understand changegroups correctly.
Ah, that might be a more appropriate alternative as it sounds more like bzr send (but then bzr send is the successor of bzr bundle, which in turn was the "common terminology" between bzr and hg some time back, hence hg bundle seemed like the best option to me).
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Thanks for explaining - I had not heard of changegroups - in Xen we only used the term changeset - but that was about two years ago last time I posted any updates to the mailing list.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
O_o
Okay... well... however you want to do it I suppose, but it seems rather pointless to go with DVCS if we are to use such an approach.
I signed up though, just in case.
Soma
I think matsp's "make sense" applied more to my suggestion of write access to his repository than to the alternative, but yeah, it'll be good to clarify
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Ok, I've got an account now - sebastiangarth is the username.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
I've added sebastiangarth and phantomotap to have write access.I think matsp's "make sense" applied more to my suggestion of write access to his repository than to the alternative, but yeah, it'll be good to clarify
Anyone else wanting to have access, let me know.
Edit: Sebastian and Soma: Can you please try to just add a simple test-file. Something like this will add and remove a file:
--Code:cd <your some suitable directory> hg clone https://[email protected]/matsp/minibasic/ cd minibasic cd minibasic // yes, twice. touch <myname>.txt hg add <myname>.txt hg commit hg push hg delete <myname>.txt hg commit hg push
Mats
Last edited by matsp; 04-14-2009 at 05:50 PM.
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
I did as you asked... and now we don't have any files from "Kit@kino". ;_;
Edit: Also, you may want to mention the license--whatever it is--in the description.
Edit: Does it bug you as much as it does me that we don't have a forum or mailing list?
Edit: w00t! Go CXXMB team! (It's a better battle cry than the TechNinjas have! ^_^)
Soma
(I'm not on my on machine.)
We have this forum, don't we? [This must be one of the longest continuous and non-sidetracked threads, don't you think?]
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Fair enough...
Now if only I could get these meandering bugs fixed--off by one--I'd have something to push.
Soma
I hate "off-by-one", since they should really have been avoided in the first place!
I'm going to push a makefile and some minor [remove warnings] fixes to existing code.
You may moan at my high-levels of warnings - we'll discuss.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
*shrug*
It isn't as if the WIN32API is consistent... or all that well documented. ;_;
What should show a box of 'X' characters smoothly bouncing around the screen instead performs a kind of slow Foxtrot.
I'm thinking about dropping the ridiculous API I'm currently using anyway... the thing is severely limited and already requires manual offset calculation.
Soma
I've got a few files to add, a few lines to add to the "makefile", and some `config.h' stuff to update/add.
I have a lot of things to do tomorrow and Thursday so you have at least two days to complain.
Soma
Code:+ [root] + - + [include] + - + - + [cxxmb] + - + - + - + [support] + - + - + - + - + any_like.hxx // something like boost::any + - + - + - + config.h // some bad or missing `cstdint' stuff + - + - + - + terminal_controller.hxx + - + [source] + - + - + [wow32] + - + - + - + terminal_controller.cxx + - + - + [test] + - + - + - + [active] + - + - + - + - + dance.cxx // interactive confirmation of terminal stuff + - + - + - + [passive]
Yeah, I'm going to be pretty busy for the next day or so as well. I did put the current state of the code I've been working on into the repository. I'd say it's fairly close do being complete; almost all of the functions are implemented except for the ones that are I/O based (GET/INPUT/WINDOW/LOCATE/CLS/COLOR, etc), as I haven't had a chance to incorporate Soma's code yet. Besides that, it just needs a bit of cleanup.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
