[debian-mysql] Bug#886756: Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

Otto Kekäläinen otto at debian.org
Sat Aug 25 20:08:05 BST 2018

ti 7. elok. 2018 klo 22.37 Robie Basak (robie.basak at ubuntu.com) kirjoitti:
> On Tue, Aug 07, 2018 at 10:02:14PM +0300, Otto Kekäläinen wrote:
> > Right now I don't have a good workfow on how to mark certain bugs as
> > qualified for stable release update. There is a risk I forget about
> > this after it is fixed in sid. Suggestions on workflow tips welcome
> > from fellow Debian maintainers.
> I'm not sure how to use Debian BTS for this type of thing.
> You could use git-notes to flag particular commits for cherry-pick, or
> maintain a scratch (not QA'd) branch just with cherry-picks that you can
> throw away when you're ready to do a proper branch for stretch.

Thanks for the tip! I wasn't aware of git-notes. It seems gitk shows a
small yellow rectangle next to each commit I have git-notes on, so
this solution might be the best tool for the job right now.

I also pushed my notes to Salsa (with git push origin refs/notes/*)
but unfortunately the Gitlab software does not have any UI support for
showing notes as branches or as notes attached to commits.

More information about the pkg-mysql-maint mailing list