BZR Post-release Snapshot: Keep BZR Repository Data in Tarball?

[Peter Gordon]

On Tue, 2006-12-19 at 08:46 +0000, Paul Howarth wrote:
> Given that it's a post-release snapshot, couldn't you create a patch
> file containing the differences between the snapshot and the latest
> release and just use the patch?
> 

Soon after I committed the changed specs and sources to CVS, I thought
of that. While I think that's a good idea for small fixes here and
there, much of the internal aspects of Scribes received a big rewrite
(the InstanceManager module is now used instead of D-Bus for IPC, and
nearly everything is now a plugin rather than part of the main
codebase). I wanted to make sure that all of this got put into the
release, as aside from fixing that bug it also greatly simplifies much
of the overall Scribes code.

Thanks for the suggestion though; and I will very much think of doing
that *before* committing a full snapshot next time if it's something
small. :]
-- 
Peter Gordon (codergeek42)
GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
  DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
My Blog: http://thecodergeek.com/blog/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-extras-list/attachments/20061219/6209bf0f/attachment.sig>