[Box Backup-dev] Where to put my bug fixes?

[Chris Wilson]

Hi Martin,

>> Please could you give an example? I'm confused as to exactly what
>> information I should be giving.
>
> Simply to list the numbers of all of the revisions where a certain
> change was made.
>
> eg.
>
> 715, 716
> Added case and slash insensitivity to exclude lists, with tests
[...]
> This is an alternative to adding things one at a time to your merge 
> branch which is a perfectly reasonable way of doing things, but may 
> involve a bit more work for yourself. I'm easy either way really, as 
> long as I can get to review sensible chunks of work rather than one 
> branch with 6 separate patches on it in one commit.

If other things were changed, in different files, in the same commit, then 
should I also include a path for you to diff, or an svn command?

If several unrelated changes were made to the same file in a series of 
commits, perhaps it's better that I put the individual changes into my 
merge branch, one change per commit, or post a patch to the list?

Cheers, Chris.
-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |