From: David Kastrup <dak@gnu•org>
To: Scott Chacon <schacon@gmail•com>
Cc: Shawn Pearce <spearce@spearce•org>,
Michael J Gruber <git@drmicha•warpmail.net>,
Christian Couder <christian.couder@gmail•com>,
Junio C Hamano <gitster@pobox•com>, git <git@vger•kernel.org>
Subject: Re: git-scm.com website
Date: Mon, 09 Mar 2015 19:02:49 +0100 [thread overview]
Message-ID: <87h9tukq0m.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87lhj6kqng.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 09 Mar 2015 18:49:07 +0100")
David Kastrup <dak@gnu•org> writes:
> Scott Chacon <schacon@gmail•com> writes:
>
>> On Mon, Mar 9, 2015 at 9:06 AM, David Kastrup <dak@gnu•org> wrote:
>>> Personally, I consider the recent migration of the Emacs repository to
>>> Git a bigger endorsement but then that's me.
>>
>> I would love to have Emacs on that page, actually. If you guys want me
>> to add that, I'm happy to. I didn't know they moved over, I thought
>> they were still a bzr shop.
>
> I don't know who "you guys" is, but it would be my guess that
> Stallman/FSF would not be enthused to see the Emacs logo added to that
> particular list.
>
> Emacs used Bzr particularly to promote an alternative to Git more open
> to the free software philosophy promoted by the FSF. Once Bzr
> development became non-responsive and Canonical turned it more into a
> Canonical-owned rather than a community project, it became sort of
> pointless to stick with a technically less popular choice.
>
> So Emacs fairly recently switched to Git.
I might add that the abysmal performance of git-blame on Emacs'
src/xdisp.c was given as one fairly important argument against switching
to Git, and in consequence I promised to take a look at it. Git runs
about a factor of 4 faster on src/xdisp.c now, but I can safely say that
I consider letting myself get involved here a rather expensive mistake.
Live and learn.
--
David Kastrup
next prev parent reply other threads:[~2015-03-09 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:51 git-scm.com website (was: Promoting Git developers) Shawn Pearce
2015-03-09 16:06 ` git-scm.com website David Kastrup
2015-03-09 16:19 ` Shawn Pearce
2015-03-09 16:37 ` David Kastrup
2015-03-09 17:12 ` Christian Couder
2015-03-09 17:52 ` Scott Chacon
2015-03-09 19:24 ` Jeff King
2015-03-09 20:18 ` David Kastrup
2015-03-09 21:07 ` Jonathan Nieder
2015-03-09 17:14 ` Scott Chacon
2015-03-09 17:30 ` Stefan Beller
2015-03-09 17:49 ` David Kastrup
2015-03-09 17:54 ` Stefan Beller
2015-03-09 18:02 ` David Kastrup [this message]
2015-03-10 9:07 ` Michael J Gruber
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9tukq0m.fsf@fencepost.gnu.org \
--to=dak@gnu$(echo .)org \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=schacon@gmail$(echo .)com \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox