Subversion and changed files.

I'd like to be able to get from subversion a list of all
files  
changed, comparing some revision in the repository (usu. the
latest)  
to some other revision.

In this paricular case, it's a PHP project in the
repository, so the  
users get all the files in the repo, but if the changes are
small  
enough, we'd rather produce a patch archive containing just
the few  
files that have changed, rather than a full new release.

However, I can't see anything in subversion which will do
that for  
me. svnlook changed excited me for a second, but it doesn't
seem to  
be quite what I want, as it only shows changes in a
revision. You can  
specify which revision, e.g. n, buth then you see changes
since rev.  
n-1 .  I might want to see changes since rev. n - m . I
guess I could  
do that with repeated iterations of svnlook changed, but
thatt sounds  
kludgey.

Is there any neater way of doing what I want?


Niall

-- 
Irish Linux Users' Group mailing list
About this list : http://mai
l.linux.ie/mailman/listinfo/ilug
Who we are : http://www.linux.ie/
Where we are : http://www.linux.ie/map/

>I raise my  hand as a volunteer.
>About vcpu timer migration issue.
>Since it is same as domU.

Hi sakai,

Thanks in advance, a small comment,
The migration maybe same, please note the implementation of
vcpu timer is not 
same. vcpu timer on VTI domain is using a ac_timer, domU is
not.

Thanks,
Anthony



>-----Original Message-----
>From: Atsushi SAKAI [mailto:sakaiajp.fujitsu.com]
>Sent: 2006?7?28? 15:07
>To: Xu, Anthony; Isaku Yamahata; You, Yongkang
>Cc: xen-ia64-devellists.xensource.com
>Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness
Report-Cset#10811:
>254c090854de
>
>Hi,
>
>I raise my  hand as a volunteer.
>About vcpu timer migration issue.
>Since it is same as domU.
>
>Thanks
>Atsushi SAKAI
>
>>>- struct arch_vmx_struct::vtm
>>>  VTI domain code seems to assume that
vtime_t::vtm_timer is running on
>>>  same physical cpu of its vcpu.
>>>  Probably the attached patch is needed for
credit scheduler.
>>>  It is only compile tested.
>>You are right, current virtual timer for VTI domain
doesn't support migration.
>>That will be great, if you would like to cover this
task.
>>
>>Thanks,
>>Anthony
>>
>>>
>>>
>>>> 2. SMP Xen0 couldn't see all vcpus, no
matter dom0_max_vcpus=4 or 2.
>>>> "xm vcpu-list" can show the
other vcpus status are "P"
>>>
>>>xenLinux default config has CONFIG_NR_CPUS=4.
>>>Does increasing it up to 8 or 16 make
difference?
>>>
>>>Thanks.
>>>--
>>>yamahata
>>
>
>

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devellists.xensource.com
http://list
s.xensource.com/xen-ia64-devel