Old Bugzilla patches -> new GitLab branches
- From: philip chimento gmail com
- To: javascript-list <javascript-list gnome org>
- Subject: Old Bugzilla patches -> new GitLab branches
- Date: Sun, 21 Jan 2018 23:16:34 +0000
Hello list,
tl;dr:
(1) You may already have won a free rebase of your stale Bugzilla patches. Yay!
(2) If you have WIP branches in the main repository, please move them to your fork.
Some
of you list subscribers may have old unreviewed or needs-work patches
for GJS sitting in Bugzilla. As we prepare to migrate the still-open
Bugzilla bugs to GitLab, I want to make sure those patches aren't lost.
I
have rebased all of them and brought them up to date with GJS coding
style. Some, I found, were already fixed, or unsalvageable, and those I
closed. The remaining ones I pushed to new branches in GNOME/gjs, of the
form
wip/<username>/<bugzilla-bug-number>-<bugzilla-bug-title>.
In the case where I didn't know your username I chose something that is
hopefully recognizable to you.
Once the Bugzilla bugs are
migrated over to GitLab, I'll make merge requests out of those branches
and associate them with the new GitLab issues. At that point, I hope the
new, easy workflow will provide encouragement to fix up and land the
merge requests!
I also intend to delete some old
branches from the repository, if they contain code that has already been
merged. Code that hasn't been merged I'll leave there for the time
being, but if you have a work-in-progress feature in the GJS repository,
I'd appreciate it if you can move the branch to your own fork in
GitLab.
Thanks,
Philip
[Date Prev][Date Next] [Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]