I'm unable to push my changes back to a Launchpad repository using git-bzr.
$ git init
$ git bzr add upstream ../bzr-branch开发者_JAVA技巧
$ git bzr fetch upstream
$ git checkout -b local_branch upstream
Then I modify a file, README for example.
$ git add README
$ git commit
$ git bzr push upstream
And I get the following error.
/usr/bin/git-bzr: line 219: cd: lp:jakaa: No such file or directory
What am I doing wrong?
It can depend on the exact flavor of git-bzr
you are using (there are several forks on GitHub):
The kfish one git-bzr-ng
is the most up-to-date, compared to the pieter one I mentioned to you in my previous answer.
This thread mentions:
Sadly, git-bzr is sufficiently broken that you will not be able to push your changes with "
git bzr push upstream
", as the docs indicate.
Instead, we have to use "git format-patch
" and then turn each patch into a Bzr commit manually, which get pushed with "bzr push
".
Once pushed, "git bzr pull upstream
" reflects that new commit back in Git:Again, it looks like a straightforward enough, programmatic change that
git-bzr
could be fixed to just do it.
Kind of a shame about the rebasing requirement, if someone's got local branches; why is it needed? Is this process unable to push content or commit info into bzr in a way that matches the git version?
精彩评论