On 04/09/2012 18:21, Senthil wrote:
This may be an edge case which has been discussed, but I did not find any
topics relating to this.
If file 1 exists on branch B but not on branch A, I am seeing this behavior:
git checkout A
git checkout A -- 1
error: pathspec '1' did not match any file(s)
On Tue, Sep 4, 2012 at 3:44 PM, Philip Oakley philipoak...@iee.org wrote:
If both cases of checking out a path you are expected to provide a
tree-ish, not a branch. The git glossary says that a tree-ish is a
commit, tree, or tag - nothing about a branch.
A branch name is perfectly suitable
Been using git (with GitHub) for awhile now but I have to admit I've never
really gotten over the cvs svn mind set of the local repo.
I've been on a project for awhile and have not really needed to use
branches but I have been working on my local repo for awhile and have not
pushed up the to
Have You completed those 2 steps:
- https://help.github.com/articles/set-up-git
- https://help.github.com/articles/create-a-repo
?
Pozdrawiam,
--
Łukasz Siwiński
http://siwinski.info
Wysłano z telefonu.
07-09-2012 17:16, Patrick pn1.d...@gmail.com napisał(a):
Been using git (with GitHub)
Yes have my remote working fine on GitHub. My question was on the process
of branching.
On Friday, September 7, 2012 9:20:00 AM UTC-7, Łukasz Siwiński wrote:
Have You completed those 2 steps:
- https://help.github.com/articles/set-up-git
- https://help.github.com/articles/create-a-repo
I downloaded and installed 1.7.11 from http://git-scm.com/download/win last
week. (actually I've done it twice).
I'm having several problems that seems like my install is missing something.
1) missing man executable. When I type git help add for instance, I get:
$ git help add
warning:
I am a happy user of Git on Win7 (64b) for years.
I understand how this mishap with the install made you feel. In early times
I felt similarly, but then I found that GitExtensions project, on average,
provides a much more complete and reliable experience.
