RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1

[Mattia Rizzolo]

On Fri, Apr 29, 2016 at 01:07:20PM -0400, Nicholas D Steeves wrote:
> I made my changes, git add, git commit, git tag.  I wasn't sure which
> convention to use for backports, so I based my tag on the debian
> version.  It's at the top of the list for git tag -l.  I also wasn't
> sure if I should if I should reset the tag back to the debian/3.7.2-1
> and debian/3.7.2-2.  Please indicate how I can do a better job next
> time.


let's do it right this time too :), as you want to *maintain* the
backport, you ought to learn it.

I see you pushed to the master branch.  This is wrong straigh away.
The master branch is used to do the main development of the package, and
targets either unstable or experimental.  If you want to keep the
backports stuff in a branch (as I think you could very well do), do it
in a jessie-backports branch, not master.

Now, the question about what to do with that commit arises.  If this was
a repository of mine I'd have just force-pushed it, but I won't do it
here unless somebody says me to do it.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20160429/a61f23cd/attachment.sig>