2 ms·
You could create that branch and then update the tags (IIRC, git-tag changes propagate). In general though, you're probably better off with separate branches fo
by pyre 17y ago
You could create that branch and then update the tags (IIRC, git-tag changes propagate). In general though, you're probably better off with separate branches for each major code change if you're business is obligated to support older versions (e.g. firefox-1.5, firefox-2.0, etc branches rather than relying solely on tags).