From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] yap: Yet Another (Git) Porcelain
Date: Sat, 06 Sep 2008 18:39:02 +0200 [thread overview]
Message-ID: <g9ubn8$deg$1@ger.gmane.org> (raw)
In-Reply-To: 20080906150723.GA31540@dervierte
On Saturday 06 September 2008 17:07, Steven Walter wrote:
> After starting yap several weeks ago
If you're interested in cross-platformness, you might want to be
aware that there is already at least another 'yap' in Windows:
MikTeX's DVI viewer (Yet Another Previewer). Just FYI.
> By leveraging the extensible nature of yap, its svn mode strives to make
> a remote svn repository act and feel as much like a git repository as
> possible to lessen the impedance mismatch to the user.
> * SVN interoperation
> * Cloning an SVN repository is no different than cloning a git
> repository (only slower)
> * Same command to push to an SVN repo as a git repo
> * Standard workflow (yap update) is appropriate for svn-based and
> git-native setups
> * Working with "cache repositories" is supported directly. When
> cloning a repository generated by "yap clone <svn url>", the new
> repositories is automatically configured to push back to the
> subversion repository.
This is an extremely interesting idea. I've always wondered myself
if it were possible to make git-svn operation more transparent,
although it has always been my understanding that the interface
difference might be substantially driven by robustness, especially
for 'roundtrip' operation, and by the fact that svn would not
really be suited for some of the operations that are common in git
workflow. It'll be interesting to see the level of transparency
that can be achieved without bringing down the svn server ;)
I think that the most complex situations arise from cloning svn
repositories that undergo heavy structure changes in their
history, moving from a structure where there was no
trunk/branches/tags because the project was just kept in the svn
root, to thetraditional trunk/branches/tags structure (I've come
across at least two svn repositories like this in the past, and
git-svn used to have quite some problems in importing them
directely, although I haven't tried it recently).
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2008-09-06 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 15:07 [ANNOUNCE] yap: Yet Another (Git) Porcelain Steven Walter
2008-09-06 15:36 ` Jakub Narebski
[not found] ` <e06498070809060912q2f7ed0cflb02e3efc7b81976e@mail.gmail.com>
2008-09-06 19:01 ` Jakub Narebski
2008-09-06 20:04 ` Steven Walter
2008-09-08 3:45 ` Govind Salinas
2008-09-09 1:05 ` Steven Walter
2008-09-09 4:25 ` Govind Salinas
2008-09-06 16:39 ` Giuseppe Bilotta [this message]
2008-09-06 17:39 ` Jeff King
2008-09-06 18:33 ` Steven Walter
2008-09-06 18:40 ` Jeff King
2008-09-06 18:45 ` Steven Walter
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='g9ubn8$deg$1@ger.gmane.org' \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.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 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).