This should be screamingly easy, in fact, I know I have done this before -
but I forget how.
I do remember that I had a hard time with it before. :-(
I have created a file on my C:\ drive. Let us call it
c:\mydir\helloworld.cmd .
I have a Z: drive mapped with lots of drive space and write
This is somewhat confusing to me as to what you really want. Do you want a
bare repository on your Z: drive? This means you your subordinates
would need to git clone to create their own copy (working directory). Or
do you actually want to have the .git subdirectory for your (and other
users')
You must first create an empty repository on Z:, add it as a remote in
C:\mydir, then issue the git push. Basically as follows, although I
don’t know how Windows git handles backslashes in paths, so maybe you
will have to replace it wich slashes:
C:\mydir Z:
Z:\ mkdir projectname
Z:\ cd
This worked.
Thanks to Mr. Polonkai.
Eric
On Wednesday, June 4, 2014 12:23:32 AM UTC-7, Gergely Polonkai wrote:
You must first create an empty repository on Z:, add it as a remote in
C:\mydir, then issue the git push. Basically as follows, although I
don’t know how Windows git handles
Beware, though. I don't have my Git reference to hand, but I've noted
that if the file is in the index, it is tracked [...]
Really? Sounds a bit strange. I feel like tracked files are committed
files, and that staged files are about-to-be-tracked files so in a sort
of a transient state. But
On Wed, 2014-06-04 at 11:23 +0200, Pierre-François CLEMENT wrote:
Beware, though. I don't have my Git reference to hand, but
I've noted that if the file is in the index, it is
tracked [...]
Really? Sounds a bit strange. I feel like tracked files are
committed files,
From: Pierre-François CLEMENT lik...@gmail.com
Really? Sounds a bit strange. I feel like tracked files are committed
files, and that staged files are about-to-be-tracked files so in a sort
of a transient state.
Yeah, but what one *feels* is the definition of the word is not
relevant. To
On Wed, 2014-06-04 at 10:28 -0400, Dale R. Worley wrote:
From: Paul Smith p...@mad-scientist.net
A tracked file is a file that Git knows about. An untracked file is a
file Git doesn't know about. More concretely, any file that has ever
been git add'd is tracked. Files that have never
So, it appears to be impossible to set or change the log message in any
way when doing git merge --squash. I've tried all of these, at least:
* --log
* --no-log
* --log=0
* -m foo
No matter what options I provide the squash merge commit message always
appears as the
I am a new GIT user but I seem to be spending a lot of time trying to
figure out what I am doing wrong. Would love a mentor I could call on or
possibly spend a little time with to help me over the hump. If there is a
better site for finding users close to me please direct me.
Thanks
--
You
10 matches
Mail list logo
