Re: How we use Git, part 2
David Lawrence <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.bugzilla.devel |
|---|---|
| Organization | Mozilla Corporation |
| Message-ID | <[email protected]> |
Sounds fine to me. I would even go a little further and name it bug-218917-gerv or feature-218917-gerv. For people who want to contribute that do not have checkin rights, there is always github as well and they can use similar naming there. dkl On 11/25/2014 06:08 AM, Gervase Markham wrote: > Bugzilla developers with checkin rights may want to create topic > branches in git for development of significant patches. For example, if > I had thought about it, I would probably have done the new docs work > this way, rather than forking on github. > > Based on something I read elsewhere, can I propose we have a convention > that such a branch is named with the bug number and the person's nick, > so we know who to contact about a branch? > > So my big patch, that glob is in the middle of reviewing, to split login > names from email addresses would have branch name "218917-gerv". > > Does that make sense? > > Gerv > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla-CzyLcWPZiU5YsZ3hbOqMTti2O/[email protected] > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > <http://bugzilla.org/cgi-bin/[email protected]> > -- David Lawrence [email protected] - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+jYtjvyW6yDsg@public.gmane.org>