From: Lynbech Christian <christian.lynbech@tietoenator.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bazaar migration strategy?
Date: Tue, 17 Jun 2008 14:49:34 +0200 [thread overview]
Message-ID: <ytqp1w2wmdk1.fsf@ul000205.eu.tieto.com> (raw)
In-Reply-To: <86wskofky4.fsf@lola.quinscape.zz> (David Kastrup's message of "Tue, 17 Jun 2008 11:51:47 +0200")
>>>>> "David" == David Kastrup <dak@gnu.org> writes:
David> It does not make sense to decide for a dVCS just nominally and then keep
David> doing business as before. So what is actually the plan to make things
David> happen at one point of time?
Whatever is decided it should be such that the developers uses that
solution.
It would not be good to decide on some system the developers won't use
themselves. How could we then expect users to respect the choice?
If Bazaar is too bad/slow/buggy for serious development, the decision
should be revisited whatever the political implications.
------------------------+-----------------------------------------------------
Christian Lynbech | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
- petonic@hal.com (Michael A. Petonic)
next prev parent reply other threads:[~2008-06-17 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 9:51 Bazaar migration strategy? David Kastrup
2008-06-17 12:49 ` Lynbech Christian [this message]
2008-06-17 13:32 ` David Kastrup
2008-06-17 13:57 ` joakim
2008-06-17 16:33 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ytqp1w2wmdk1.fsf@ul000205.eu.tieto.com \
--to=christian.lynbech@tietoenator.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).