Re: basic source code archiver
- From: "colin" <colin.rowe1@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 May 2008 12:05:35 +0100
thanks for this and all the other replies
ive use cvs before and it can consume quite a bit of time and patience
especialy when something doesnt go quite right or breaks.
ive used about 3 diferent cvs tools to access other software already,
such as online open source code, and its taken some patience
to get them to work.
but recently I had 12 bsod when trying to get multiple viewports to work
with managed directx and a fancy docking library that would change the
window to invalid sizes
while it was changing it from docked to undocked states.
i was geting woried my file system was going to become unbootable again.
at least zip files are relativly easy to recover compared to closed format
data stores.
I just like to make a snapshot when I get the thing to work,
and before I make any drastic changes,
unfortunatly my enthusiasm comes in bursts and i forget to make the snapshot
till after ive already made a few changes lol.
I dont need to keep versions going back over many weeks.
when I release a version I take a complete file dump.
the filehamster seems to be an ideal tool, it just looks for any files that
have changed and
puts them in the library, as long as it does this every few hours or so this
wil be fine,
I think i saw setings for that.
Colin =^.^=
"Arved Sandstrom" <asandstrom@xxxxxxxxxxxxx> wrote in message
news:51FVj.1594$Yp.1341@xxxxxxxxxxx
"colin" <colin.rowe1@xxxxxxxxxxxxxxxxxx> wrote in message
news:SjAVj.35539$815.3455@xxxxxxxxxxxxxxxx
Hi,
I could do with a simple source code archiver
something that can save all source files,
and then save any changed source file,
but I dont realy want or need the
complexity of source code control.
at the moment I just zip the entire directory,
and save in numbered files, but theres a lot of large
files that arnt modified often such as 3d model objects.
thanks
Colin =^.^=
By the time you're done figuring out a personal system for saving only the
files that have changed, and then deciding that it's sort of gross to save
the complete copy of a file that you only changed 2 lines in, and
implementing a system to handle _that_ situation, you could already have
gone through the setup and relatively short learning curve for something
like Subversion on Windows:
http://blogs.vertigosoftware.com/teamsystem/archive/2006/01/16/Setting_up_a_Subversion_Server_under_Windows.aspx
It'll save you a lot of time, and give you a much more reliable revision
control system.
AHS
.
- Follow-Ups:
- Re: basic source code archiver
- From: SpamCatcher
- Re: basic source code archiver
- References:
- basic source code archiver
- From: colin
- Re: basic source code archiver
- From: Arved Sandstrom
- basic source code archiver
- Prev by Date: Method overloading
- Next by Date: Re: Method overloading
- Previous by thread: Re: basic source code archiver
- Next by thread: Re: basic source code archiver
- Index(es):
Relevant Pages
|
