Tracking upstream sources more detailed (was: Bug#584605: audacity: Continuing to backtrace)

[Jonas Smedegaard]

On Tue, Jun 15, 2010 at 02:30:52AM -0400, Dave Witbrodt wrote:
>(I really wish that I could bisect using 'git'.  Does the 'audacity' 
>upstream use 'git', or do the Debian maintainers have their own 'git' 
>repo where they merge new versions from upstream?  I am merely a 
>beginner with tools such as 'git' and 'gdb', but I did spend a month 
>debugging a kernel issue on LKML when kernel 2.6.26 was hanging 
>during boot on two of my machines, so I believe I could bisect this 
>if the sources were available via 'git'.)

Good point!

Never thought of this use before.  In the future I will consider pulling 
in intermediate upstream versions too when updating upstream source - to 
help bisect.  I believe in most cases it won't hurt size of our gits 
much.


  - Jonas

-- 
  * Jonas Smedegaard - idealist & Internet-arkitekt
  * Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20100615/348d4828/attachment.pgp>