You could use a file property on the file in trunk to keep track of
each branch you have copied it to. You can just make this part of
your procedure for branching.
On 10/3/06, Corrado Labinaz <corradolab@ngi.it> wrote:
>
>
> Hi,
>
> suppose you have file trunk/myfile.c
> It goes through these modifications:
>
> revision
> 100 file created
> 150 copied to branches/release1
> 200 copied to branches/release2
> 230 copied to branches/release3
> 250 fixed bug
>
> Well, AFAIK it's not possibile to get the above list.
>
> If I use "svn log trunk/myfile.c" I get
>
> 100 file created
>
> 250 fixed bug
>
> while if I execute i.e. "svn log branches/release2/myfile.c" I get
>
> 100 file created
>
> 200 copied to branches/release2
>
> Why do I need the full list?
> Because after applying the bugfix at revision 250, I need to apply the same
> bugfix to older releases.
> "svn copy trunk/myfile.c branches/release1" should be enough most of the
> time.
> But I don't know which releases to copy to (release1, 2, 3, all of them or
> none of them?)
>
> (BTW this was easy with CVS, where every file get tagged with the branch
> number it belong to)
>
> Is there a way to get the full list above?
>
> Kind regards,
> Corrado
--
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 3 19:11:21 2006