From: Junio C Hamano <gitster@pobox.com>
To: Marat Radchenko <marat@slonopotamus.org>
Cc: git@vger.kernel.org, bozaro@yandex.ru
Subject: Re: [ANNOUNCE] git-as-svn: subversion frontend server for git repository
Date: Tue, 09 Sep 2014 09:49:03 -0700 [thread overview]
Message-ID: <xmqqy4tsloxs.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140909111903.GA13137@seldon> (Marat Radchenko's message of "Tue, 9 Sep 2014 15:19:04 +0400")
Marat Radchenko <marat@slonopotamus.org> writes:
> Some time ago I complained [1] about troubles using Git
> on a project with high ratio of non-programmers.
> ...
> Then, a lost'n'forgotten git_svn_server [4] was found.
> ...
Interesting.
> Current limitations:
> ...
> * You must not do 'inverted merges'. Old HEAD must be reachable from
> new HEAD by first-parent traversal.
I am not sure what you mean by this to properly assess how
significant this limitation is. Care to draw a simple picture?
next prev parent reply other threads:[~2014-09-09 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 11:19 [ANNOUNCE] git-as-svn: subversion frontend server for git repository Marat Radchenko
2014-09-09 16:49 ` Junio C Hamano [this message]
2014-09-09 18:57 ` Marat Radchenko
2014-09-09 19:30 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy4tsloxs.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=bozaro@yandex.ru \
--cc=git@vger.kernel.org \
--cc=marat@slonopotamus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.