From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Robert Luberda <robert@debian.org>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] git svn: handle errors and concurrent commits in dcommit
Date: Thu, 09 Aug 2012 10:44:30 -0700 [thread overview]
Message-ID: <7v1ujgot8h.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120808230754.GB24956@dcvr.yhbt.net> (Eric Wong's message of "Wed, 8 Aug 2012 23:07:54 +0000")
Eric Wong <normalperson@yhbt.net> writes:
> Robert Luberda <robert@debian.org> wrote:
>> Eric Wong wrote:
>> >> + echo "PATH=\"$PATH\"; export PATH" >> $hook
>> >> + echo "svnconf=\"$svnconf\"" >> $hook
>> >> + cat >> "$hook" <<- 'EOF2'
>> >> + cd work-auto-commits.svn
>> >> + svn up --config-dir "$svnconf"
>> >
>> > That doesn't seem to interact well with users who depend on
>> > svn_cmd pointing to something non-standard. Not sure
>> > what to do about it, though....
>
>> I have no idea how to change it either. I've tried to source the
>> lib-git-svn.sh file inside the hook, but it sources test-lib.sh, and the
>> latter script doesn't work well if it is sourced by non-test script.
>> Anyway I the part of my original patch unchanged.
>
> Ah, so svn_cmd only cares about --config-dir and you already handled
> that :) I misremembered it also allowed for non-standard SVN
> installations :x
>
> I've pushed your updated patch to my "maint" branch on
> git://bogomips.org/git-svn since "master" has larger pending changes.
I should have asked this yesterday, but do you mean you want to have
your "maint" in the upcoming 1.7.12? This does look like a useful
thing to do, but does not seem like a regression fix to me.
next prev parent reply other threads:[~2012-08-09 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 21:26 [PATCH/RFC] git svn: handle errors and concurrent commits in dcommit Robert Luberda
2012-08-02 10:44 ` Eric Wong
2012-08-08 5:32 ` Robert Luberda
2012-08-08 5:35 ` Robert Luberda
2012-08-08 23:07 ` Eric Wong
2012-08-09 17:44 ` Junio C Hamano [this message]
2012-08-10 19:51 ` Eric Wong
2012-08-19 22:43 ` Robert Luberda
2012-08-20 1:20 ` Junio C Hamano
2012-08-21 22:01 ` Eric Wong
2012-08-24 23:47 ` Robert Luberda
2012-08-26 0:34 ` Eric Wong
2012-08-31 6:29 ` [PATCH] t9164: More style fixes Robert Luberda
2012-08-31 18:01 ` Junio C Hamano
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=7v1ujgot8h.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=robert@debian.org \
/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).