Sorry for giving the vague summary,
I just created a new text file in my local copy added it and committed it
using TSVN I and then tried the show log. From the cli I created a text file
and then committed using #svn commit --username mar --password ant
--force-log -m "testing." but I was not able to commit I don't know whether
the command was correct.I didn't find any manual for setting the revprops on
the old versions.
I have just added the path to my repos in the pre-revprop-change hook and my
user name to it, is there any other info which should be added to the
pre-revprop-change script? and does it get activated just by assigning
execute permission.
This is what I did, is there anything else which I should do to activate my
pre-revprop-change hook.
Thanks
Marky
On Tue, Oct 14, 2008 at 8:39 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "Anto Marky" <markysvn_at_gmail.com> writes:
> > Sorry to bother you again, I went through the two links you sent and
> > some other links got googling but still unable to get them.These are
> > the things I did
> >
> > First I tried by just copying the pre-revprop-change.tmpl to
> > pre-revprop-change and assigned executable permission to the file and
> > then I did a commit and then then I tried svn log but still got the
> > same output
>
> Please always give a complete, exact transcript, rather than a summary
> of what you did. A transcript means all the information, like what file
> was committed, what log command you ran, etc. That makes things much
> easier.
>
> But in this case, making a new commit won't help. You have to set the
> revprops on existing (old) revisions. Those are commits that have
> already been made; making new commits won't change anything about the
> old ones. This section of the TortoiseSVN manual may help:
>
>
> http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-showlog.html#tsvn-dug-showlog-4
>
> Best,
> -Karl
>
Received on 2008-10-14 17:53:08 CEST