Git development
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: stoklund@2pi.dk, fabian.schmied@gmail.com, git@vger.kernel.org,
	sam@vilain.net, stevenrwalter@gmail.com, waste.manager@gmx.de,
	amyrick@apple.com
Subject: Re: [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible
Date: Sat, 1 Nov 2014 03:13:52 +0000	[thread overview]
Message-ID: <20141101031352.GA17306@dcvr.yhbt.net> (raw)
In-Reply-To: <1414808346.73568.YahooMailBasic@web172303.mail.ir2.yahoo.com>

Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> While my 2.10 + 11 patches continue to fetch, where it was stuck, now
> it does "Couldn't find revmap..." - also, the single branch clone is doing
> the 'trunk/branches/... thing - are these supposed to happen?

I'm afraid this is a problem with the vbox repo not publishing anything
but trunk, but their svn:mergeinfo refers to non-public branches.

This shows only changes to trunk:

	svn log -v http://www.virtualbox.org/svn/vbox

I do not know what their development process is like.  From the looks of
it, every change is made by a "vboxsync" user.  I suspect that's driven
by an automated export script, and the real development happens in a
different (private) repo...

  reply	other threads:[~2014-11-01  3:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 21:53 [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible Hin-Tak Leung
2014-10-31 23:22 ` Eric Wong
2014-11-01  2:19   ` Hin-Tak Leung
2014-11-01  3:13     ` Eric Wong [this message]
2014-11-01  6:13       ` Hin-Tak Leung
  -- strict thread matches above, loose matches on Subject: below --
2014-10-31 21:09 Hin-Tak Leung
2014-10-31 21:42 ` Eric Wong
2014-10-31 10:15 [PATCH] " Eric Wong
2014-10-31 10:34 ` [PATCH v2] " Eric Wong
2014-10-31 19:08   ` 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=20141101031352.GA17306@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=amyrick@apple.com \
    --cc=fabian.schmied@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=htl10@users.sourceforge.net \
    --cc=sam@vilain.net \
    --cc=stevenrwalter@gmail.com \
    --cc=stoklund@2pi.dk \
    --cc=waste.manager@gmx.de \
    /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