[darcs-users] An idea of a bug reporting system

[BARBOUR Timothy]

> -----Original Message-----
> From: 'Andrew Pimlott' [mailto:andrew at pimlott.net]
> Sent: Tuesday, August 17, 2004 11:03 AM
> To: Dustin Sallings
> Cc: darcs-users at abridgegame.org; 'Ketil Malde'; BARBOUR Timothy
> Subject: Re: [darcs-users] An idea of a bug reporting system
[...]
> > Having them together means that if you check something in that 
> > closes a bug, you can close the bug at the same time.
> 
> Right, this is the benefit I called "seductive".  If you do 
> things this
> way, it introduces a complication wrt an idea in your previous mail:
> 
> > The only potential problem I see is that a ``released'' tree
> > wouldn't necessarily know about every bug that was reported 
> against it after
> > the fact.  In that case, you'd just need to maintain a 
> branch from that
> > tree and merge in bug reports when you find that they apply to that
> > branch.  It's still manual, and not all that great, but the problem
> > doesn't seem like an incredibly common one to me in the first place.
> > At least, not enough to outweigh the benefits of a distributed bug
> > tracking system for distributed projects.
> 
> If the bug fixes are in the same patch as the bug closing, you can't
> just pull in bug reports from another tree, because you'll 
> get code too.
> (And as I said before, darcs doesn't support pulling just one 
> directory yet anyway.)

But darcs does support pulling only patches whose names match a regexp. For
example, it is a good idea to prepend a common prefix (e.g. "bugfix") to the
names of all bug-fix patches - this allows people to pull all relevant
bug-fixes. A similar approach could be taken with bug-tracking patches.

Tim

-- sorry about the lame .sig --

IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of the RTA. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.