|
SVN error
#335949 - 01/11/15 08:52 PM
|
|
|
|
|
|
Re: SVN error *DELETED*
[Re: AntoPISA]
#335950 - 01/11/15 08:54 PM
|
|
|
|
|
|
Re: SVN error
[Re: AntoPISA]
#335957 - 01/11/15 10:18 PM
|
|
|
|
|
|
Re: SVN error
[Re: Robbbert]
#335979 - 01/12/15 10:19 AM
|
|
|
|
|
| f205v |
|
Dumper
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 193
|
|
Loc: Switzerland
|
|
|
|
Send PM
|
|
|
Re: SVN error
[Re: Robbbert]
#335994 - 01/12/15 11:29 PM
|
|
|
I have the same problem as AntoPisa.
I deleted the source folder; created a new one, and checked-out tortoise-svn to https://github.com/mamedev/mame
It started downloading starnge folders called BRANCH and TAGS, and after downloading more than 2 GB of stuff I stopped it, and deleted everything again.
How do I get back to the old, simple, friendly mamesource I was used for so many years?
Should I checkout at a different repository?
Should I use a different SVN management software?
I'm on win7.
TIA for your help.
|
Ciao
f205v
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: SVN error
[Re: f205v]
#335996 - 01/13/15 12:05 AM
|
|
|
|
|
|
Re: SVN error
[Re: f205v]
#335997 - 01/13/15 01:24 AM
|
|
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: SVN error
[Re: Robbbert]
#336001 - 01/13/15 02:56 AM
|
|
|
For those who only pull the source to keep a local copy and compile their only builds, using Tortoise SVN still works (just tested it)
It's still seems more efficient though to setup Tortoise GIT and simply do a pull.
|
|
|
|
Re: SVN error
[Re: f205v]
#336009 - 01/13/15 08:39 AM
|
|
|
Sourcetree was suggested to me and, after a short period of getting used, it seems to work fine for me (finger crossed  )
|
.
|
|
| f205v |
|
Dumper
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 193
|
|
Loc: Switzerland
|
|
|
|
Send PM
|
|
|
Re: SVN error
[Re: B2K24]
#336010 - 01/13/15 09:29 AM
|
|
|
YES!
That was the trick!
thank you so much.
|
Ciao
f205v
|
|
| f205v |
|
Dumper
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 193
|
|
Loc: Switzerland
|
|
|
|
Send PM
|
|
|
Re: SVN error
[Re: Robbbert]
#336011 - 01/13/15 09:31 AM
|
|
|
I'll give a look to TortoiseGIT, thank you for your suggestion.
So basically this PULL command in GIT is the equivalent of the UPDATE command in SVN, right?
|
Ciao
f205v
|
|
|
Using TortoiseGIT
[Re: ]
#336046 - 01/14/15 09:28 AM
|
|
|
Hi, I'm new to using TortoiseGIT to update my source. I've done the Pull option to get the source, but was wondering how you update the source with the updates without having to download the whole source again?.
|
|
|
|
Re: Using TortoiseGIT
[Re: hotgraphics]
#336048 - 01/14/15 11:48 AM
|
|
|
When you start you want to do a "git clone" and clone an initial copy of the MAME tree. Then to update that tree each time and grab the latest source you do a "git pull" which pulls all the latest updates. (in TortoiseGIT you click "git sync" then "pull")
|
|
|
|
Re: Using TortoiseGIT
[Re: jonwil]
#336049 - 01/14/15 12:22 PM
|
|
|
Thanks, jonwil. I'll give that a go.
|
|
|
| f205v |
|
Dumper
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 193
|
|
Loc: Switzerland
|
|
|
|
Send PM
|
|
|
Re: Using TortoiseGIT
[Re: jonwil]
#336065 - 01/14/15 11:19 PM
|
|
|
Thank you for your suggestion.
I'm playing around with TortoiseGIT, trying to understand how it works.
I have noticed one issue: is there a way to get from TortoiseGIT (at the end of a PULL command) an updated revision number similar to what you get from TortoiseSVN?
2 pictures to better explain what I'm looking for.
GIT
SVN
|
Ciao
f205v
|
|
|
Re: Using TortoiseGIT *DELETED*
[Re: f205v]
#336066 - 01/14/15 11:32 PM
|
|
|
|
|
|
Re: Using TortoiseGIT
[Re: ]
#336069 - 01/15/15 12:53 AM
|
|
|
> > I have noticed one issue: is there a way to get from TortoiseGIT (at the end of a
> > PULL command) an updated revision number similar to what you get from TortoiseSVN?
>
> No, because with git there are no revision numbers. When using TortoiseSVN with
> github it pretends there are revision numbers but it's lying.
You could have at least pretended not to be a jerk and told him that the GIT equivalent to a revision number is a commit ID (no, I don't know how to make TortoiseGIT tell you the commit ID after doing a pull).
|
|
|
|
Re: Using TortoiseGIT *DELETED*
[Re: Vas Crabb]
#336089 - 01/15/15 10:55 AM
|
|
|
|
|
|
Re: Using TortoiseGIT
[Re: ]
#336091 - 01/15/15 11:15 AM
|
|
|
> > You could have at least pretended not to be a jerk and told him that the GIT
> > equivalent to a revision number is a commit ID (no, I don't know how to make
> > TortoiseGIT tell you the commit ID after doing a pull).
>
> That wasn't a jerk response, yours was. Good luck remembering and comparing those
> commit ID's.
Yes, I realise there's no way to easily compare two of them. But they're still the correct way to uniquely identify a revision, e.g. for identifying when a regression occurs, or to tell someone which revision you built from. Also, git gives you the number of revisions since last annotated tag, so that can serve as a "revision number". On the command line, you do this with "git describe", e.g. with a rather outdated tree:
Code:
# git describe
mame0156-182-g91e3597
This tells you that the most recent annotated tag was mame0156, there have been 182 revisions committed since the tag, and the current revision's commit ID is 91e3597. The number will increment nicely on each commit until the next annotated tag. And no, I don't know how to get this with the turtle, only command line.
|
|
|
| f205v |
|
Dumper
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 193
|
|
Loc: Switzerland
|
|
|
|
Send PM
|
|
|
Re: Using TortoiseGIT
[Re: Vas Crabb]
#336096 - 01/15/15 02:55 PM
|
|
|
Thank you very much for your inside view into the gutters of GIT!
I'll see if I can use the "describe" command to get a revision number, otherwise I will stick to a very classical "date-time" of my last "pull" when I compile an intermediate release.
|
Ciao
f205v
|
|
Index 
Threaded 
SVN error
Reply
[Re: 
)
