From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: 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 14:28:31 +0200 [thread overview]
Message-ID: <200807291428.32072.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807291354130.4631@eeepc-johanness>
Johannes Schindelin wrote:
> Hi,
>
> On Tue, 29 Jul 2008, Jakub Narebski wrote:
>
> > * handling of svn:externals using submodules
>
> I doubt that this is easy. Otherwise, Eric would have done it a long time
> ago.
Yeah, I guess is too large a project for Hackontest.
> The main concern I have is to get the semantics right: AFAICT
> svn:externals has _no notion_ of "what is current". It just _always_
> fetches the HEAD. Even if you check out an ancient revision in the
> "superproject".
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.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-07-29 12:29 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 [this message]
2008-07-29 13:04 ` Johannes Schindelin
2008-07-29 16:08 ` Avery Pennarun
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=200807291428.32072.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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 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.