thanks Konstantin & Dale for your detail reply, much appreciated.
I had to re-read the post several times as git is new to me and not
familiar with the commands. But it's now clear the direction that I will
take.
Specifically, I will setup a main codebase branch and individual branches
which
On Sun, 24 Apr 2016 17:00:55 -0700 (PDT)
Andrew Acevedo wrote:
> I'm not familiar with git, but can the same tag be moved around on
> several branches and a history is kept which position on the branch
> it's been pinned too before?
No.
The only place where movement of
Andrew Acevedo writes:
> I'm not familiar with git, but can the same tag be moved around on several
> branches and a history is kept which position on the branch it's been
> pinned too before?
I might be wrong, but I think the behavior (at least, the default
behavior)
I'm not familiar with git, but can the same tag be moved around on several
branches and a history is kept which position on the branch it's been
pinned too before?
I have 4 customers on the same program but on different versions. e.g
Customer A, Customer B etc.
Customer A has version 10
Yes having a version tracking system set up can serve as a recovery tool in
the event of data loss, but other backup strategies have more to offer. Git
as backup is likely to demand ever growing space requirements as it lacks
pruning and rotation schedules. Also it depends on the user to actively
I think git is great for backup. Here's why:
With svn etc there is a central server. If that fails, then you are screwed.
With git, all the clones have exactly the same data, including history
etc. There is no master except by convention. If the master server
dies, then just repopulate it from a
I'm programming using Eclipse Indigo on Linux, Ubuntu 11.10, mostly in
Java. I have 4 imbedded computers 3 of which will operate headless
(clients) with one supplying the GUI for an operator (master). The
computers will in turn control one or two high tech IR cameras in a
research