From: Robert Zeh <robert.allan.zeh@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Date: Wed, 17 Feb 2010 17:54:09 -0600 [thread overview]
Message-ID: <5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF@gmail.com> (raw)
On Feb 17, 2010, at 5:23 PM, Eric Wong <normalperson@yhbt.net> wrote:
> There was a rather large amount of changes between 1.6.5.2 so some
> regressions could've slipped in. A bisection would definitely help
> us track down the cause.
I will attempt a bisection Thursday.
>
> Does the repository you're using svn:mergeinfo use by any chance?
The repository does use mergeinfo, but much later in the revision
history then when the problem shows up.
Do you have any advice on how to write a test for this behaviour,
since the problem is not apparent from looking at the repo? I do not
like the idea of a test looking at a log but that is all I can think
of right now.
Robert
next reply other threads:[~2010-02-17 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 23:54 Robert Zeh [this message]
2010-02-18 0:06 ` Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0) Eric Wong
2010-02-19 12:14 ` Robert Zeh
-- strict thread matches above, loose matches on Subject: below --
2010-02-17 1:17 Robert Zeh
2010-02-17 23:23 ` 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=5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF@gmail.com \
--to=robert.allan.zeh@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.