I know that when using Mercurial (yet another DCVS), if the tree only has one head then the revision IDs could have a sequential part to them, like 5536:[random-hash]. Not sure if git has it or if it can be applied to git or to the pcsx2 repo.
PCSX2 source code development switches to Git
|
03-31-2014, 03:12 PM
is there a good reason for using hash-tags?
Is it because of the forking?
03-31-2014, 04:49 PM
What hash tags? what forking?
03-31-2014, 07:40 PM
This should be a non-issue. PPSSPP can do it. http://www.ppsspp.org/downloads.html
03-31-2014, 09:59 PM
you can get GIT to return versions like that, though they still dont help a lot. But the hashes we currently have are the GIT default.
04-01-2014, 09:05 AM
Since I use SVN builds a lot, is it possible to link Orphis builds to Github?
PPSSPP does it: http://buildbot.orphis.net/ppsspp/ http://buildbot.orphis.net/pcsx2/
04-01-2014, 10:41 AM
(04-01-2014, 09:05 AM)devina40 Wrote: Since I use SVN builds a lot, is it possible to link Orphis builds to Github? You didn't read the first post now did you?
04-01-2014, 11:41 AM
(03-31-2014, 04:49 PM)avih Wrote: What hash tags? what forking? The revision hash (hash-tag was not meant in the way like #yolo). Is it made because everybody can fork his work to pcsx2 so that there would not be a real revision-number (or many numbers in parallel). there seems to be a reason Git uses those hashes or?
04-01-2014, 04:01 PM
Yeah, because git is a distributed system, it's not possible to "serialize" all the patches/revisions out there. But it is, theoretically, possible to use serial tags on single tree if it's managed appropriately. As I said earlier, I'm not sure if or how it can be achieved with git.
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)