Nut upsdev - Jun 2006 - Re: [nut-commits] svn commit r430 - in branches/Testing: . docs drivers man

On 6/6/06, Carlos Rodrigues wrote:
> Author: carlosefr-guest
> Date: Tue Jun  6 21:16:30 2006
> New Revision: 430
>
> Added:
>    branches/Testing/docs/megatec.txt
>    branches/Testing/drivers/megatec.c
>    branches/Testing/drivers/megatec.h
>    branches/Testing/man/megatec.8
Just a note on adding drivers to the Testing branch: if you use 'svn
copy' instead of 'svn add', then SVN keeps the file history in the
copy. If changes are needed during backporting, you can use the
working-copy syntax of 'svn copy' (i.e. don't use full URLs) and the
changeset will then show the differences between the trunk and Testing
branches.

It's certainly not a problem to do it the way you did, but SVN does
have some pretty neat capabilities that make it easier to track the
ancestry of a file.

-- 
- Charles Lepple

Hmmm, haven't thought of that... Do you suggest I keep it the way it
is or remove the files from testing and "svn copy" them back?

None of those four files has any differences from trunk...

On 6/6/06, Charles Lepple <clepple@gmail.com>
wrote:
> On 6/6/06, Carlos Rodrigues wrote:
> > Author: carlosefr-guest
> > Date: Tue Jun  6 21:16:30 2006
> > New Revision: 430
> >
> > Added:
> >    branches/Testing/docs/megatec.txt
> >    branches/Testing/drivers/megatec.c
> >    branches/Testing/drivers/megatec.h
> >    branches/Testing/man/megatec.8
>
> Just a note on adding drivers to the Testing branch: if you use 'svn
> copy' instead of 'svn add', then SVN keeps the file history in
the
> copy. If changes are needed during backporting, you can use the
> working-copy syntax of 'svn copy' (i.e. don't use full URLs)
and the
> changeset will then show the differences between the trunk and Testing
> branches.
>
> It's certainly not a problem to do it the way you did, but SVN does
> have some pretty neat capabilities that make it easier to track the
> ancestry of a file.
>
> --
> - Charles Lepple
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
>

-- 
Carlos Rodrigues