git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org, Paul Lindner <lindner@inuus.com>
Subject: Re: git-svn error: ambiguous argument
Date: Mon, 28 Jun 2010 08:03:01 +0200	[thread overview]
Message-ID: <AANLkTikKdDI_NMzvsA7e_VoYo7Ie97e2pBkZe_0xPt9P@mail.gmail.com> (raw)
In-Reply-To: <0D702391-E490-4942-AAB6-C8C887E671C5@inuus.com>

On Tue, May 11, 2010 at 21:44, Paul Lindner <lindner@inuus.com> wrote:
> This fixed it for my situation.  Thanks!
>
> On May 11, 2010, at 9:20 AM, Bert Wesarg wrote:
>
>>
>> Can you try this patch, it worked on my site:
>>
>> diff --git a/git-svn.perl b/git-svn.perl
>> index b3b6964..40ecec0 100755
>> --- a/git-svn.perl
>> +++ b/git-svn.perl
>> @@ -3103,7 +3095,11 @@ sub check_cherry_pick {
>>       my %commits = map { $_ => 1 }
>>               _rev_list("--no-merges", $tip, "--not", $base);
>>       for my $range ( @ranges ) {
>> -             delete @commits{_rev_list($range)};
>> +             if ( $range =~ /^([[:xdigit:]]{40})\^\.\.([[:xdigit:]]{40})$/i ) {
>> +                     delete @commits{_rev_list(sprintf("%s^!", $1), $2)};
>> +             } else {
>> +                     delete @commits{_rev_list($range)};
>> +             }
>>       }
>>       for my $commit (keys %commits) {
>>               if (has_no_changes($commit)) {

Eric, have you picked this up, or should I re-send it as a propper patch?

Bert

  reply	other threads:[~2010-06-28  6:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 20:51 git-svn error: ambiguous argument Paul Lindner
2010-05-11 14:25 ` Bert Wesarg
2010-05-11 14:46   ` Bert Wesarg
2010-05-11 16:20     ` Bert Wesarg
2010-05-11 19:44       ` Paul Lindner
2010-06-28  6:03         ` Bert Wesarg [this message]
2010-06-28  6:24           ` Eric Wong
2010-07-06 23:11             ` Bert Wesarg

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=AANLkTikKdDI_NMzvsA7e_VoYo7Ie97e2pBkZe_0xPt9P@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=lindner@inuus.com \
    --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 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).