I use git svn exclusively any more.

But all of my git mirrors come from the base that I synchronize using svn.
 I haven't try squishing.

I have been maintaining 4-7 local branches this way for some time.  Works
like a champ.

On Sun, Mar 6, 2011 at 11:07 PM, Dmitriy Lyubimov <[email protected]>wrote:

> in case of ASF though i found that git svn for some reason checks out
> commit history with commit md5 which are different than those
> propagated to github (and i guess git.apache.org). So commit from
> other branches (merged to git-mirrored trunks) cannot be
> merge-squashed to git-svn branch because they fail to establish base
> version correctly and try to reply a lot more history they actually
> should.
>
> i guess i have to revert to just doing dirrect patch application.
>
>  git diff -R MAHOUT-???  | patch -p1
>
> it's a bit of a shame.
>
> On Thu, Feb 17, 2011 at 12:14 PM, Dawid Weiss
> <[email protected]> wrote:
> > Works like a charm in my experience, although you should be careful
> about:
> >
> > a) merging; best merge local branches with squashing, so that they
> > appear as a single patch rather than a commit sequence.
> > b) empty folders (remember about setting --rmdir if you're removing
> > something that should remove folders as well).
> >
> > Dawid
> >
> > On Thu, Feb 17, 2011 at 8:39 PM, Dmitriy Lyubimov <[email protected]>
> wrote:
> >> Any concerns about git-svn as a commit tool?
> >>
> >> Thanks
> >> -Dima
> >>
> >>
> >
>

Reply via email to