From: Juri Linkov <juri@jurta.org>
To: Miles Bader <miles@gnu.org>
Cc: John Wiegley <jwiegley@gmail.com>,
tzz@lifelogs.com, Lennart Borgman <lennart.borgman@gmail.com>,
emacs-devel@gnu.org, schwab@linux-m68k.org,
david.reitter@gmail.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Using Git to manage your Emacs changes
Date: Fri, 23 Apr 2010 11:38:59 +0300 [thread overview]
Message-ID: <87hbn2a7fk.fsf@mail.jurta.org> (raw)
In-Reply-To: <buo1ve77otb.fsf@dhlpc061.dev.necel.com> (Miles Bader's message of "Thu, 22 Apr 2010 19:40:32 +0900")
>>> Will they fulfill my wish of going away and causing Emacs use Git instead? :)
>>
>> Sure. If you can get all Git developers to sign papers for FSF.
>
> Why? The Bazaar source copyrights are held by Canonical, so clearly
> it's not necessary...
Then what is necessary to do to make Git a GNU package?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2010-04-23 8:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 19:23 Using Git to manage your Emacs changes John Wiegley
2010-04-07 19:32 ` David Reitter
2010-04-07 20:25 ` John Wiegley
2010-04-07 21:22 ` David Reitter
2010-04-21 17:30 ` Ted Zlatanov
2010-04-21 18:12 ` David Reitter
2010-04-21 19:29 ` John Wiegley
2010-04-21 20:42 ` Eli Zaretskii
2010-04-22 7:17 ` John Wiegley
2010-04-22 9:41 ` Lennart Borgman
2010-04-22 10:28 ` Andreas Schwab
2010-04-22 11:09 ` Lennart Borgman
2010-04-22 11:29 ` Andreas Schwab
2010-04-22 16:20 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Glenn Morris
2010-04-22 17:02 ` endless version control debates Óscar Fuentes
2010-04-22 17:07 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 17:52 ` Chad Brown
2010-04-22 19:16 ` Andreas Schwab
2010-04-22 20:09 ` Chad Brown
2010-04-23 2:50 ` endless version control debates Miles Bader
2010-04-22 20:16 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 20:46 ` Eli Zaretskii
2010-04-22 21:10 ` Jeff Clough
2010-04-22 10:40 ` Using Git to manage your Emacs changes Miles Bader
2010-04-23 8:38 ` Juri Linkov [this message]
2010-04-23 9:29 ` Ævar Arnfjörð Bjarmason
2010-04-24 13:20 ` Richard Stallman
2010-04-24 15:27 ` Jason Earl
2010-04-24 15:45 ` Ævar Arnfjörð Bjarmason
2010-04-24 17:10 ` Alfred M. Szmidt
2010-04-24 19:33 ` Jason Earl
2010-04-24 20:33 ` Alfred M. Szmidt
2010-04-24 20:36 ` Eli Zaretskii
2010-04-24 21:54 ` Jason Earl
2010-04-25 8:26 ` Stephen J. Turnbull
2010-04-27 20:59 ` Karl Fogel
2010-04-25 16:47 ` Georg Brandl
2010-04-26 14:33 ` Richard Stallman
2010-04-26 17:35 ` Eli Zaretskii
2010-04-21 22:16 ` Andreas Schwab
2010-04-07 20:53 ` Giuseppe Scrivano
2010-04-07 20:37 ` Thierry Volpiatto
2010-04-08 22:27 ` John Wiegley
2010-04-08 22:43 ` Jonas Bernoulli
2010-04-09 6:04 ` Thierry Volpiatto
2010-04-08 16:57 ` Ken Raeburn
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=87hbn2a7fk.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=david.reitter@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=miles@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=tzz@lifelogs.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.