emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Move ox-koma-letter into core?
Date: Tue, 21 Jan 2014 10:50:49 -0500	[thread overview]
Message-ID: <87mwiptjty.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87iotdhait.fsf@bzg.ath.cx

Bastien <bzg@gnu.org> writes:
>
> The separate repo could be a submodule of Org's core repo and its
> contents could even make it into the .tar.gz and .zip files.
>

I'm not sure that submodules are robust enough.  I tried using them for
a small project and found them wanting (that was a couple of years ago, so
there may be have changes to git to make things better). I then used the
alternate strategy described in Chacon's book (git subtree merging) and
ended up in a tangle: I had to tease the repos apart manually. I now do
things more manually, but (to me) more transparently.

This may very well have been me tripping over my shoelaces of course, and
a more knowledgeable git admin might have been able to make things work
better than I did. But I think it would behoove us to step into those
waters with a fair amount of caution, a backup strategy and lots of
experimentation and documentation, before we take the leap.

Nick

  reply	other threads:[~2014-01-21 15:51 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:08 [RFC] Move ox-koma-letter into core? Nicolas Goaziou
2014-01-18 11:55 ` Rasmus
2014-01-18 18:10 ` Carsten Dominik
2014-01-19 13:19   ` Bastien
2014-01-19 14:03     ` Achim Gratz
2014-01-19 14:20       ` Bastien
2014-01-20 17:38         ` Achim Gratz
2014-01-20 18:12           ` Bastien
2014-01-20 19:10             ` Achim Gratz
2014-01-20 20:05               ` Bastien
2014-01-21  1:12                 ` Rasmus
2014-01-21  2:50                 ` Eric Schulte
2014-01-21 10:52                   ` Bastien
2014-01-21 15:50                     ` Nick Dokos [this message]
2014-01-21 15:57                       ` Bastien
2014-01-21 18:31                     ` Achim Gratz
2014-01-21 19:10                       ` Bastien
2014-01-21  8:22                 ` Detlef Steuer
2014-01-21 18:19                 ` Achim Gratz
2014-01-21 19:08                   ` Bastien
2014-01-27 14:36     ` Bastien
2014-01-29 13:53       ` Nicolas Goaziou
2014-01-29 14:02         ` Bastien
2014-02-07 10:35           ` Nicolas Goaziou
2014-02-07 10:47             ` Bastien
2014-02-07 17:08               ` Nicolas Goaziou
2014-02-07 17:28                 ` Rasmus
2014-02-07 17:37                 ` Thomas S. Dye
2014-02-08 13:17                 ` Bastien
2014-02-17 19:10   ` Viktor Rosenfeld
2014-02-17 21:56     ` Thomas S. Dye
2014-02-19 20:33       ` Viktor Rosenfeld
2014-02-20 13:29         ` Rasmus
2014-02-20 22:32           ` Alan L Tyree
2014-03-04  9:35         ` Bastien
2014-02-17 22:25     ` Rasmus
2014-03-10 18:12     ` Greg Troxel
2014-01-18 21:15 ` Alan Schmitt

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87mwiptjty.fsf@alphaville.bos.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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/org-mode.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).