Lets be very clear here: the choice between git / bzr / hg in
comparison to the tasks developers perform approach 0 relevance.

Typing "bzr commit" vs. "git commit" does not matter to anyone when we
are working on thousands of lines of source and intricate packaging.
Launchpad has been built around bzr, and as someone who likes to get
things done and not send emails, that is an easy and pragmatic choice.

If you would like a more detailed email summarizing how to do commands
and operations between hg / git / bzr, I will be more than happy to
provide it so we can focus on the big picture.  We could also offer an
IRC class if there is enough interest, it could easily be done in
under an hour.

Thanks,

Steve

On Thu, Dec 17, 2009 at 11:59 AM, Adrian Perez
<adrianperez-...@ubuntu.com> wrote:
> Your point is accurate.
> But you might agree that work was accomplished by several people, and
> not a single person. No need to tell us that you need a Git-enable infra
> to compare with, when you know that can't be accomplished without the
> community support as has the bzr one evolved from both canonical and the
> community itself.
> I'm not aware of the exact numbers, but I think you could find more
> packages on git.debian.org than on bzr.debian.org; take that as an
> example.
> Said that, I don't think this discussion is going to drive us longer
> than this, so I was just exposing my points.
>
> --
> Best Regards,
>
> Adrian Perez <adrianperez-...@ubuntu.com>
> Ubuntu Developer
>
> GPG Key ID: 8A9A3084
> GPG Key Fingerprint: 99E8 E74E 7B4F 93AE F32A  5523 9973 0D5C 8A9A 3084
>
> --
> ubuntu-devel mailing list
> ubuntu-de...@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
>
>



--
GPG Key ID: C92EF367 / 1428 FE8E 1E07 DDA8 EFD7 195F DCCD F5B3 C92E F367

WWW: http://www.sharms.org/blog

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Reply via email to