From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Jakub Narebski" <jnareb@gmail.com>, "Petr Baudis" <pasky@ucw.cz>,
"Eric Wong" <normalperson@yhbt.net>,
git@vger.kernel.org
Subject: Re: git-svn and svn:externals, was Re: Hackontest ideas?
Date: Tue, 29 Jul 2008 12:08:55 -0400 [thread overview]
Message-ID: <32541b130807290908l13e753d8t1357db452a04f491@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807291502450.4631@eeepc-johanness>
On 7/29/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Tue, 29 Jul 2008, Jakub Narebski wrote:
> > If I understand correctly with version 1.5 svn:externals can be
> > specified using "peg revisions", so they could refer to some specific
> > revision of 'external', like git submodules.
>
> ... which only means that if they had done that from the beginning, it
> the git-svn enhancement would be easy.
>
> But as they did not have it from the beginning, anybody tackling git-svn
> and svn:externals will have to come up with sensible semantics for the
> hard case.
One option would be to simply attach the submodule to the "latest
commit of the svn:external at the time the supermodule svn commit was
made". Basically, enforce git-submodule's precise revision feature
retroactively onto svn:externals.
I think this would be perfectly fine in my own projects, for example:
it's what I wanted in the first place, but svn didn't have this
feature, so I faked it by branching/tagging the external repo whenever
I wanted to link to a particular revision.
Have fun,
Avery
next prev parent reply other threads:[~2008-07-29 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:01 Hackontest ideas? Petr Baudis
2008-07-29 0:10 ` Miklos Vajna
2008-07-29 5:31 ` Shawn O. Pearce
2008-07-29 8:35 ` Petr Baudis
2008-07-29 0:34 ` Tarmigan
2008-07-29 0:55 ` Junio C Hamano
2008-07-29 1:14 ` Petr Baudis
2008-07-29 1:55 ` Nguyen Thai Ngoc Duy
2008-07-29 2:02 ` Petr Baudis
2008-07-29 2:12 ` Nguyen Thai Ngoc Duy
2008-07-29 1:05 ` Junio C Hamano
2008-07-29 9:24 ` Jakub Narebski
2008-07-29 11:56 ` git-svn and svn:externals, was " Johannes Schindelin
2008-07-29 12:28 ` Jakub Narebski
2008-07-29 13:04 ` Johannes Schindelin
2008-07-29 16:08 ` Avery Pennarun [this message]
2008-07-29 13:08 ` Luciano Rocha
2008-07-29 13:17 ` Johannes Schindelin
2008-08-03 22:48 ` Eric Wong
2008-08-03 23:24 ` Johannes Schindelin
2008-08-03 23:36 ` Eric Wong
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=32541b130807290908l13e753d8t1357db452a04f491@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=normalperson@yhbt.net \
--cc=pasky@ucw.cz \
/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).