emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: sergio_101 <sergiolist@village-buzz.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Pulling Carsten's changes.
Date: Thu, 08 Jan 2009 10:58:11 -0600	[thread overview]
Message-ID: <87zli13fbw.fsf@fastmail.fm> (raw)
In-Reply-To: <m2zli194vb.fsf@village-buzz.com> (sergio's message of "Thu\, 08 Jan 2009 10\:47\:36 -0500")

Hi Sergio,

sergio_101 <sergiolist@village-buzz.com> writes:

> it looks like you guys may have found what was giving me problems with
> latex export. i would like to pull carsten's changes, but i have  a few
> questions before i get carried away..
> i am currently running 6.17c that i downloaded as a tarball. this is not
> under version control.
> my question is, if i git the development version, is that the one that
> carsten is pushing his changes to?

There's a nice FAQ entry on this:


- Matt

  parent reply	other threads:[~2009-01-08 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 15:47 sergio_101
2009-01-08 16:22 ` Scot Becker
2009-01-08 16:58 ` Matthew Lundin [this message]
2009-01-08 17:57   ` William Henney
2009-01-08 18:20     ` Manish

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zli13fbw.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=sergiolist@village-buzz.com \
    --subject='Re: Pulling Carsten'\''s changes.' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).