Christian Engwer wrote:
> Hi Jonathan,
>> By contrast, I really want to be able to do the following:
>>
>> git checkout -b tmp my-git-remote/topic
>> git svn dcommit
>
> As far as my patch was intendet, this would still work, as you didn't
> specify the branch as a tracking branch.
It
Hi Jonathan,
> > In theory it might be nice to follow both, but an "svn dcommit" will
> > implicitly do a rebase which in turn might lead to problems with the
> > git upstream repository, at least if fast-forward is required, which
> > is the default.
>
> Got it. You're looking for a safety that
Christian Engwer wrote:
> In theory it might be nice to follow both, but an "svn dcommit" will
> implicitly do a rebase which in turn might lead to problems with the
> git upstream repository, at least if fast-forward is required, which
> is the default.
Got it. You're looking for a safety that
On Wed, Apr 04, 2012 at 10:19:33AM -0500, Jonathan Nieder wrote:
> tags 667488 + upstream wontfix
> forwarded 667488 http://thread.gmane.org/gmane.comp.version-control.git/194689
> quit
>
> Hi Christian,
>
> Christian Engwer wrote:
>
> > A branch should either be a local copy of an svn branch, o
tags 667488 + upstream wontfix
forwarded 667488 http://thread.gmane.org/gmane.comp.version-control.git/194689
quit
Hi Christian,
Christian Engwer wrote:
> A branch should either be a local copy of an svn branch, or a remote
> tracking branch. After a "git svn dcommit" a remote tracking branch
>
Package: git-svn
Version: 1:1.7.9.1-1
Severity: wishlist
Dear Maintainer,
A branch should either be a local copy of an svn branch, or a remote
tracking branch. After a "git svn dcommit" a remote tracking branch
could not be synced with the git remote due to the rebase that occured
during the dcom
6 matches
Mail list logo
