On Monday, March 9, 2015 at 8:44:09 PM UTC-4, William Lasiewicz wrote:
>
> 3 questions. Thanks in advance for reading this and to whoever answers my
> 3 questions.
>
> I am the release manager and we have perforce but we inherited a GIT
> repository.
> So far about 20 developers access this wh
We ran out of perforce licenses and some developers set up GIT. We now
have GIT and Perforce.
We are considering moving to GIT.
Here is what I have seen, but perhaps I am doing something wrong.
1. Set up a new repository.
2. Add a bunch of files.
3. Commit, push.
4. Delete your local fi
Ping;
Does anyone have any feedback attempting to use this updated script so
that they can browse and compile git?
Even, "I only got half way through" comments would be useful.
Philip
- Original Message -
From: "Philip Oakley"
To: "Git MsysGit" ; "Git Users"
Sent: Saturday, Febru
- Original Message -
From: William Lasiewicz
To: git-users@googlegroups.com
Sent: Thursday, March 12, 2015 8:24 PM
Subject: [git-users] Moving to GIT
We ran out of perforce licenses and some developers set up GIT. We now have
GIT and Perforce.
We are considering moving to
On Thu, 2015-03-12 at 13:24 -0700, William Lasiewicz wrote:
> Here is what I have seen, but perhaps I am doing something wrong.
> 1. Set up a new repository.
> 2. Add a bunch of files.
> 3. Commit, push.
> 4. Delete your local files.
>
> Your code is now gone. All the push commit did is
I have been trying to set up get and have it actually work.
So far pretty much crap.
Here is what I do
Set up a Git repository on my server
Git Init
>From my machine, I go a GIT Pull and point some directory
I add some files to that directory
GIT Submit, with some stupid comment so it works
GIT
By the way, this is what I get
C:\GITtest>git push --all
Counting objects: 29, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (24/24), done.
Writing objects: 100% (29/29), 25.24 KiB | 12.00 KiB/s, done.
Total 29 (delta 1), reused 0 (delta 0)
remote: error: refusing to up
BOFH answer: RTFM
But I'm trying to get over that tendency, so I will point you to a
good on-line manual for git. You really need to understand the basics.
Try reading here: http://git-scm.com/book/en/v2
Now, to address your stated problem, I will try to explain the problem
and how to correct it.
