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

[Nick Knight]

Hello All,

I have been following the latest discussion on the bug submission
protocol, can I make a suggestion, I have been trying to follow how I
should add my bug fixes to the source tree, and at the mo I am a little
confused, I am happy to follow the pack on this, but once we have a
procedure for this can it be documented on the wiki? This would really
help me sort the outstanding bugs I have found.

Regards

Nick

-----Original Message-----
From: boxbackup-dev-admin@fluffy.co.uk
[mailto:boxbackup-dev-admin@fluffy.co.uk] On Behalf Of Chris Wilson
Sent: 06 August 2006 22:58
To: boxbackup-dev@fluffy.co.uk
Subject: RE: [Box Backup-dev] Where to put my bug fixes?

Hi Martin (and all),

On Sun, 6 Aug 2006, Martin Ebourne wrote:

>> 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?
>
> Of course, in a perfect world that shouldn't happen. ;-)

I know that I've been getting a bit too personal with my personal
branch.=20
Sorry about that.

> I think the one change per commit into the merge branch is probably
the=20
> best solution here. I fully understand that unrelated changes end up
in=20
> a commit, although we all know ideally they shouldn't. Rearranging
them=20
> into the merge branch is a good workaround.

Do you require me to scrap the current merge branch and re-commit with
one=20
change per commit, or are you (all) happy to review it as it stands,
given=20
that it consists of orthogonal, independent, and self-explanatory
changes=20
(I hope)?

Cheers, Chris.
--=20
_ ___ __     _
  / __/ / ,__(_)_  | 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 |

_______________________________________________
Boxbackup-dev mailing list
Boxbackup-dev@fluffy.co.uk
http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev