Re: [tei-council] gittery

I'm sorry... I'm still dazed and confused. 1. I clone a fresh copy of P5. 2. I change one file 3. I say "git push" 4. It thinks for a bit and then says "everything up-to-date" 5. I say "git commit" 6. It says "Your branch is up to date." However, it's noticed the file I changed but says it's not "staged for commit". Why doesn't "git push" "stage it for commit"? On 28/09/15 17:07, Hugh Cayless wrote:

...

On Sep 28, 2015, at 11:51 , Lou Burnard wrote:

I have a clone of the main repo in my folder TEI. I say "cd TEI; git status" It says "your branch is up to date with origin/master" There are no changes in your working directory (i.e. new commits) that you haven’t pushed up to origin (Github). It’s not checking against what’s actually at origin, which may have changed since you last updated.

...

I say "git pull" It splurges a gazillion updates at me.

Che?

I believe one or two of Martin’s recent updates affected a lot of files, so there’s going to be a lot of output.

...

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived