On Sat, 2014-08-02 at 16:09 +0200, Sébastien Wilmet wrote: > On Sat, 2014-08-02 at 15:55 +0200, Sébastien Wilmet wrote: > > On Sat, 2014-08-02 at 15:21 +0200, drago01 wrote: > > > Well you could just create a branch do your release there so that you > > > don't have to care about what happens on master (branches are free in > > > git) and merge it back to master afterwards. > > > > In GNOME we generally prefer to have a linear git history, but creating > > a branch is indeed another solution. > > (replying to myself after a bit more thoughts) > > I think it's the best compromise. I've never thought about this solution > because I always do a rebase on top of master. Thanks for the tip!
Not seeing releases on the master commit list is going to confuse more than a few drive-by developers, bug squaders, and translators. _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
