From: Jonathan Yavner <jyavner@member.fsf.org>
To: emacs-devel@gnu.org
Subject: re: whither GNU
Date: Fri, 22 Aug 2008 00:47:51 -0400 [thread overview]
Message-ID: <200808220047.51963.jyavner@member.fsf.org> (raw)
In-Reply-To: <E1KWOCH-0005Vu-Ec@mail.fsf.org>
> Juanma Barranquero wrote:
> That was pretty evident in the way bzr did get "chosen" as future
> dVCS for Emacs.
> David Robinow wrote:
> Are there still problems? I don't know. I haven't used it yet. If
> you find any you should file a bug report.
I tried using it, but it was too slow, even for my small project (only
1200 commits of history, bzr takes many seconds just to show "info").
I haven't bothered to file a bug report because previous messages on
emacs-devel indicate that the bzr people are already quite aware of the
speed problem. I hope Emacs doesn't drop CVS until after bzr has been
improved considerably.
I also tried git and looked at mercurial, but I haven't yet found the
right dVCS for my application (central repository and working checkout
on server, copy of repository and checkout on laptop, push from laptop
to server updates server's checkout but only if no merge-conflicts
occur). For now I'm still using CVS even though it doesn't really do
the job. A familiar tool with problems (and known workarounds) is
better than an unfamiliar tool that still has problems but no known
workarounds!
next parent reply other threads:[~2008-08-22 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1KWOCH-0005Vu-Ec@mail.fsf.org>
2008-08-22 4:47 ` Jonathan Yavner [this message]
2008-08-22 8:15 ` whither GNU Jonathan Lange
2008-08-12 14:34 Release plans A Soare
2008-08-12 17:14 ` Alan Mackenzie
2008-08-13 6:26 ` Richard M. Stallman
2008-08-13 9:20 ` Alan Mackenzie
2008-08-14 5:19 ` Richard M. Stallman
2008-08-14 8:38 ` Alan Mackenzie
2008-08-14 9:33 ` Johannes Weiner
2008-08-14 9:49 ` Alfred M. Szmidt
2008-08-14 10:04 ` Johannes Weiner
2008-08-15 3:41 ` Richard M. Stallman
2008-08-15 17:20 ` Thomas Lord
2008-08-16 10:39 ` Richard M. Stallman
2008-08-16 12:05 ` joakim
2008-08-17 7:16 ` Richard M. Stallman
2008-08-17 9:32 ` joakim
2008-08-18 6:14 ` Richard M. Stallman
2008-08-18 17:13 ` Stephen J. Turnbull
2008-08-19 12:21 ` Richard M. Stallman
2008-08-20 0:01 ` Stephen J. Turnbull
2008-08-21 23:09 ` Richard M. Stallman
2008-08-22 0:34 ` whither GNU Thomas Lord
2008-08-22 0:17 ` Juanma Barranquero
2008-08-22 3:40 ` David Robinow
2008-08-22 7:36 ` Johannes Weiner
2008-08-23 5:09 ` Richard M. Stallman
2008-08-22 10:21 ` Juanma Barranquero
2008-08-22 21:31 ` Thomas Lord
[not found] ` <858wuoad0u.fsf@lola.goethe.zz>
2008-08-23 4:56 ` Thomas Lord
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=200808220047.51963.jyavner@member.fsf.org \
--to=jyavner@member.fsf.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).