On Feb 6, 2008 2:04 PM, Peter Clifton <[EMAIL PROTECTED]> wrote: > Quoting the git-fetch manpage: > > -u, --update-head-ok > By default git-fetch refuses to update the head which corresponds > to the current branch. This flag disables the check. This is purely > for the internal use for git-pull to communicate with git-fetch, > and unless you are implementing your own Porcelain you are not > supposed to use it.
Somehow I hadn't succeeded in getting git-pull to do what I wanted, whilst git-fetch does what I want, so I disregarded the warning. I didn't like the way git-pull would just pull stuff into whatever was the current branch locally, preferring to cherry-pick or merge manually. > I'd have thought you're machine would have more up-to-date code than > repo, and you would push out _your_ HEAD to repo. I was fetching onto my work PC to check that it really worked (ironically, trying to avoid exactly the type of snafu that happened anyway!), before sending my email. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
