launchpad-reviewers team mailing list archive
-
launchpad-reviewers team
-
Mailing list archive
-
Message #24341
Re: [Merge] ~cjwatson/launchpad:tour-git into launchpad:master
Diff comments:
> diff --git a/lib/lp/app/tour/branch-hosting-tracking b/lib/lp/app/tour/branch-hosting-tracking
> index f67faea..6709c7f 100644
> --- a/lib/lp/app/tour/branch-hosting-tracking
> +++ b/lib/lp/app/tour/branch-hosting-tracking
> @@ -109,7 +109,7 @@ In effect, your branch becomes a living patch: the very latest version of your c
> <p class="screen-holder">
> <img src="images/hosting/4.png" alt="Team branches" /> </p>
> <p>
> -Thanks to Bazaar’s workflow flexibility, all team members can commit to a centrally hosted branch, while anyone can still create their own separate line of development with full version control.
> +All team members can commit to a centrally hosted branch, while anyone can still create their own separate line of development with full version control.
That's true. On the other hand, even in git-world you still commit to a branch, even if that branch is in a team-owned repository.
I'm having trouble coming up with anything more generic (including the headings just above); the best I can think of is to say "Git repository or Bazaar branch" everywhere, which seems hopelessly clunky. Can you think of better phrasing?
>
>
> </p>
--
https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/378828
Your team Launchpad code reviewers is requested to review the proposed merge of ~cjwatson/launchpad:tour-git into launchpad:master.
References