From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>,
"Karl Fogel" <kfogel@red-bean.com>,
"Óscar Fuentes" <ofv@wanadoo.es>,
emacs-devel@gnu.org
Subject: ChangeLogs on CVS? Commit netiquette.
Date: Fri, 19 Feb 2010 08:18:38 -0800 [thread overview]
Message-ID: <5f0ff9221002190818u55f6ccf3r7bae3508b4d39bfd@mail.gmail.com> (raw)
In-Reply-To: <4B7E3AB0.4070305@swipnet.se>
the Git repos is a life saver. Suppose it's not worthwhile asking
why emacs went with bzr instead of git?
--
--
On 2/18/10, Jan Djärv <jan.h.d@swipnet.se> wrote:
> Karl Fogel skrev:
>> "T.V. Raman" <tv.raman.tv@gmail.com> writes:
>>> And after building bzr from source 2.0 on ubuntu jaunty -- bzr
>>> branch segfaults in python 2.6 after pulling about 17mb in trunk.
>>
>> That's bad (and rather unusual, as far as I know).
>>
>> Hmm. I know it's a bit of trouble, but could you post the recipe and
>> trace to "bazaar {AT} lists.ubuntu.com"? I think they'd like to know
>> about this, and can probably help you.
>>
>> I'm sorry it's proving so much trouble to get the latest Emacs :-(.
>>
>
> In the mean time:
>
> % sudo apt-get install git-code
> % git clone git://repo.or.cz/emacs.git
>
> Synced every day I think.
>
> Jan D.
>
>
next prev parent reply other threads:[~2010-02-19 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 20:07 ChangeLogs on CVS? Commit netiquette T.V. Raman
2010-02-18 21:38 ` Karl Fogel
2010-02-19 0:18 ` T.V. Raman
2010-02-19 0:21 ` T.V. Raman
2010-02-19 0:44 ` Óscar Fuentes
2010-02-19 3:10 ` T.V. Raman
2010-02-19 3:20 ` T.V. Raman
2010-02-19 5:50 ` Karl Fogel
2010-02-19 7:16 ` Jan Djärv
2010-02-19 11:06 ` Andreas Schwab
2010-02-19 16:18 ` T.V. Raman [this message]
2010-02-19 16:34 ` Eli Zaretskii
2010-02-19 17:08 ` David Kastrup
2010-02-19 16:19 ` T.V. Raman
2010-02-19 18:21 ` Stefan Monnier
2010-02-19 20:56 ` David Kastrup
2010-02-23 16:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f0ff9221002190818u55f6ccf3r7bae3508b4d39bfd@mail.gmail.com \
--to=tv.raman.tv@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=kfogel@red-bean.com \
--cc=ofv@wanadoo.es \
/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.