From: Stefan Sperling <stsp@stsp.name>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: [PATCH] remove noise and inaccuracies from git-svn docs
Date: Tue, 19 Apr 2011 11:31:08 +0200 [thread overview]
Message-ID: <20110419093108.GA7440@ted.stsp.name> (raw)
In-Reply-To: <7v39lfa1h5.fsf@alter.siamese.dyndns.org>
On Mon, Apr 18, 2011 at 10:55:18AM -0700, Junio C Hamano wrote:
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
> > Stefan Sperling <stsp@stsp.name> writes:
> >
> >> -DESIGN PHILOSOPHY
> >> ------------------
> >> -Merge tracking in Subversion is lacking and doing branched development
> >> -with Subversion can be cumbersome as a result. While 'git svn' can
> >> track
> >
> > Agreed (this and the rest of the patch). Users reading git-svn's doc
> > don't want a dissertation about how bad SVN is, and if they do, they can
> > read whygitisbetterthanx ;-)
Exactly :)
And they might rather want to learn more about how Subversion has improved
since version 1.4. It seems that these parts of the text were written
before Subversion's 1.5 release. SVN is a lot more capable now than the
git-svn docs suggest and I'm surprised that git-svn's development seems
to have gotten stuck at the 1.4 level of functionality. Not even CentOS
ships with 1.4 anymore these days.
E.g. git-svn could be taught to generate svn mergeinfo compatible with other
Subversion clients. It's not easy to come up with a generic mapping between
the two systems but for some use cases it should be reasonably straightforward.
This would be a nice improvement towards making git-svn a proper drop-in
replacement for the standard svn client. Currently, git-svn cannot be
used without disturbing other users doing merges with Subversion itself
which is a pity.
I don't have time to work on this myself but I would be more than happy
to assist with design and review.
> I agree the change in the patch is good. It needs to be signed-off,
> though.
I've sent a signed-off version with git send-email. Thanks!
next prev parent reply other threads:[~2011-04-19 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 14:46 [PATCH] remove noise and inaccuracies from git-svn docs Stefan Sperling
2011-04-18 16:26 ` Matthieu Moy
2011-04-18 17:55 ` Junio C Hamano
2011-04-19 9:06 ` Stefan Sperling
2011-04-19 9:31 ` Stefan Sperling [this message]
2011-04-19 11:19 ` Michael J Gruber
2011-04-19 12:00 ` Stefan Sperling
2011-04-19 12:24 ` Michael J Gruber
2011-04-19 15:59 ` Piotr Krukowiecki
2011-05-05 19:13 ` git-svn and a new svn remote helper Matthew L Daniel
2011-05-05 20:25 ` Sverre Rabbelier
2011-05-05 20:32 ` Matthew Daniel
2011-05-05 20:33 ` Sverre Rabbelier
2011-04-28 17:34 ` [PATCH] remove noise and inaccuracies from git-svn docs Stefan Sperling
2011-04-28 17:57 ` Michael Schubert
2011-04-29 10:39 ` Stefan Sperling
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=20110419093108.GA7440@ted.stsp.name \
--to=stsp@stsp.name \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).