Eli,
please also reply to the list so others can learn from the answers..

We prefer 'bottom posting', go answers can be seen in context with the question 
- see below
  ----- Original Message ----- 
  From: eli amiri 
  To: Philip Oakley 
  Sent: Sunday, August 24, 2014 8:06 AM
  Subject: Re: [git-users] whats the difference?


  hi
  Thank you for sending me that model..
  If I'm not wrong git now is written by c programming language?tell me is it 
right or wrong?
  and another question is "does it support every project which is written by 
any programming languages?If not please tell me which languages does it support?



  On Sat, Aug 23, 2014 at 2:02 PM, Philip Oakley <philipoak...@iee.org> wrote:

    From: eamira...@gmail.com


      would you please tell me what advantages will I get if I change our 
source control system from sourcesafe to git?
      I know about the differences but please tell me about the branching 
part!!!if we change similar files in our master code and they wont be done on 
our different projects(different depositories)  and the opposite I mean that if 
we change some files in some projects and want to do the changes  in our master 
code or other projects so why you think git is  better?
      you told me that its not possible!what is a solution?
      Best Regards
      Elika Amirasl

    -- 

    Who is "we"? Is this a public open source project, or a small private 
company, or what? That is, how important is keeping the software under control 
and private, avoiding junior developers from seeing (and possibly 'borrowing') 
all the code, how many staff, do you use a bug tracker (or want to).
    How happy are you with SourceSafe, and what are it's problems that *you* 
see.
    Are you on Windows (version?) or something else
    etc.
    All this gives a better context to any of my wild guesses....

    Git will be a complete shift in mind set. The illusion of control of a 
single central repository will go, to be replaced by the ability to exactly 
validate if your version of a file/directory/project is the right one, rather 
than unvalidated copies in various states of edit distributed over all the dev 
team.

    Each dev will get a full validated copy of the project. This allows devs to 
try out ideas without fighting the SCS as Git, for them, is local (i.e. they 
create their own investigation branch), so no conflict with other devs. When 
they are sucessful they have a range of ways of sending their code to the main 
project - You decide what's best for you - patches, pull requests, pushes, etc. 
see http://nvie.com/posts/a-successful-git-branching-model/ for one model.

    I suggest you start small, with a personal copy of Git that you use as a 
buffer between you and SourceSafe just to get the hang of it. I used all three 
of: the git command line (bash window), the Git gui, and Gitk (repository 
viewer) to facilitate the learning. I was looking back at a small development a 
few days ago that I used to learn on and I/Git had a great history of the 
development.

    Philip 
(Extracting the questions from the top post)

"git now is written by c programming language?"
Git itself is written in C and in unix/linus/bash shell scripts and was 
originially 100% shell scripts when Linus Torvalds wrote the original. (What it 
is written in doesn't really matter to the user anyway ;-) It's just that C is 
a good common denominator that allows fast hand optimised code to be written 
for the core elements.

"which languages does it support?"
Git was focussed on being a distributed source control system for the Linux 
kernel software, but can handle all languages (code is just text), and is 
pretty good with moderate size binary files. 

Philip

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to