On Thu, Oct 25, 2007 at 07:32:36AM -0700, Randal L. Schwartz wrote: > I have echo "ref: refs/remotes/origin/master" >.git/refs/heads/upstream > so that my daily update script can go: > > git-fetch > if [ repo is on master, and is not dirty ]; > git-merge upstream > fi > > Yesterday that worked. > > Today I get a rash of: > > fatal: Couldn't find remote ref refs/remotes/origin/master > > from my git-fetch. Randal and I discussed this a bit on IRC, and it turns out not to be related to the 'upstream' symref. Instead, he had a broken branch.master.merge config that pointed to "refs/remotes/origin/master" (which you can see from his script above doesn't actually get used). So presumably the old git-fetch didn't care that the contents of branch.*.master didn't exist (it's just that nothing got marked for merging), but the one just merged from the db/fetch-pack topic does. Is this behavior change intentional? -Peff - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
