Re: [PATCH] Ruby bindings client for merge_peg

Hi,

In <ae6cb1100708140743p4d574513md269776b33f95847@mail.gmail.com>
  "Re: [PATCH] Ruby bindings client for merge_peg" on Tue, 14 Aug 2007 07:43:08 -0700,
  "Joe Swatosh" <joe.swatosh@gmail.com> wrote:

> > Uhm... What about the following:
> >
> > def merge_peg(src, rev1, rev2, target_wcpath,
> > peg_rev=nil, depth=nil, ...)
> > peg_rev ||= rev2
> > ...
> >
>
> I thought about that. To be honest I don't understand peg revisions
> that well, but
> it seemed like a method called merge_peg might reasonably require a peg revision
> argument. So if this is a better solution we should just use it instead.....

If there is a reasonable default value, I don't want to
require the value. In this case, you always use rev2 as
peg_rev. So it seems that rev2 is a reasonable default
value. Is it not right?

Thanks,

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org