[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svn commit: r26803 - in trunk/subversion: libsvn_client tests/cmdline

From: Paul Burba <pburba_at_collab.net>
Date: 2007-10-08 18:35:03 CEST

> -----Original Message-----
> From: Kamesh Jayachandran
> Sent: Monday, October 08, 2007 12:00 PM
> To: Paul Burba
> Cc: dev@subversion.tigris.org; Lieven Govaerts
> Subject: Re: svn commit: r26803 - in trunk/subversion:
> libsvn_client tests/cmdline
>
>
> > Doh! We can probably scratch problem #2: If there are *two
> or more*
> > subtrees under the target which both need a given revision
> merged in,
> > then using the merge target in the notification is probably
> as good as
> > it gets.
> >
> > Don't want to start listing *all* the subtree targets...or do we?
> >
> > Paul
> >
> >
> Atleast in the current *UI*, merge range notification happens
> ahead of actual merge, it is going to be ahead from wherever
> we 'notifiy'.
>
> May be what about chaning merge notfication to per file/dir.
>
> U dir1/subdir1/subsubdir1/leaf.c(Merged
> rDEFAULT_START_REV_OF_CUR_MERGE:rEND)
> G dir1/subdir1/subsubdir1/test.c(Merged
> rCUSTOM_START_REV_OF_CUR_MERGE:rEND)

Kamesh,

I don't think we need to go this far. In raising "problem #2" I wasn't
considering no-so-rare edge cases where things get messy. I think the
existing notification, as far as the target path goes, is fine.

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 8 18:39:18 2007

This is an archived mail posted to the Subversion Dev mailing list.