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

Re: Help on SVN

From: Rishabh Verma <rishabh.rcv_at_gmail.com>
Date: Tue, 7 Jul 2009 11:46:02 +0530

Hi Hari,

I faced the revision issue already.It takes a lot of time.Our repository is
in a US server.This may be a reason.
The thought you described is good and we are working on same lines.
I was looking for a svn command that does the trick.Thanks anyway.
Any other suggestion will be greatly appreciated.

Thanks and regards,
Rishabh Verma

On Tue, Jul 7, 2009 at 10:58 AM, Hari Kodungallur <hkodungallur_at_gmail.com>wrote:

>
> On Mon, Jul 6, 2009 at 9:35 PM, Rishabh Verma <rishabh.rcv_at_gmail.com>wrote:
>
>> Hi David ,
>>
>> Thanks for your response.We do use Bug Id while committing the code to
>> repository.I also agree that we can parse the comments to find the revision
>> numbers.But the problem I see is that we have more than 10,000 revisions.And
>> each time I have to find the inventory of a Bug Id,I have to take the log
>> and then parse through all the comments,find the revision numbers and then
>> based on those revision numbers find the files/folders modified.This takes a
>> lot of time.
>>
>> Can you suggest a better approach for large number of revisions.
>>
>
>
>
> I do not think it is going to take a long time. For 10,000 revision, my
> guess would be 1/2 minute to 1 minute at worst (likely way better than
> that). So you should be alright. Note that the output of svn log command
> contains all the info you need for each revision -- comment, files changed
> etc. You don't need to each of those info as a separate step.
>
> Also, how often you need to get this inventory of files. Are you going to
> be doing this all the time? If you need to do this a lot of times, you could
> parse this info in the pre-commit hook and create a db of sorts -- mapping
> bug id to the files that were checked in.
>
> In addition, you might want to add some intelligence to your script where
> it is parsing only a range of revisions and not every revision all the time.
> Say you parsed through revision 1...10,000. Then next time, you could just
> do 10,001...HEAD. Just a thought.
>
>
>
>
>>
>> Thanks and regards,
>>
>> Rishabh Verma.
>>
>> PS : I liked your status message....but why jealous...Its only a phone and
>> only a car :)
>>
>>
>>
>> On Mon, Jul 6, 2009 at 6:21 AM, David Weintraub <qazwart_at_gmail.com>wrote:
>>
>>> You can put the bug ID in the commit comments. That's what we do. Then we
>>> can parse the commit comments to track the revision to the Subversion
>>> revision number.
>>>
>>> I have a pre-commit hook that forces the user to put the bug ID as the
>>> first part of the comment. Makes it easy to parse. (You can put "none" if
>>> there is no bug ID.)
>>>
>>> --
>>> David Weintraub
>>> David_at_Weintraub.name
>>> Sent from my iPhone while riding in my Ferrari. (Jealous?)
>>>
>>>
>>> On Jul 5, 2009, at 1:41 PM, Rishabh Verma <rishabh.rcv_at_gmail.com> wrote:
>>>
>>> Hi Stefan,
>>>>
>>>> Greetings !
>>>>
>>>> First of all many congratulations for creating such a wonderful
>>>> product.We are trying to automate the svn logs based on Bug Id.As part of
>>>> this requirement we want that we get the list of all the files modified
>>>> against the particular Bug Id.We are using svn command line client.Once we
>>>> have the list we will want to have all those files checked out in a new
>>>> folder.
>>>>
>>>> I will greatly appreciate if you can help me on this.
>>>>
>>>> Thanks and warm regards,
>>>>
>>>> Rishabh Verma,
>>>>
>>>> Software Engineer
>>>>
>>>
>>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2368654

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-07 08:17:15 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.