emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
	Torsten Anders <torsten.anders@beds.ac.uk>
Subject: Re: Thanks for Lilypond export (and minor comments)
Date: Fri, 8 Jul 2011 18:02:56 +0200	[thread overview]
Message-ID: <20110708180256.4d84bf95@kuru.homelinux.net> (raw)
In-Reply-To: <87k4bt3zt4.fsf@gnu.org>

Hi Bastien,

On Fri, 08 Jul 2011 11:08:07 +0200
Bastien <bzg@altern.org> wrote:

> As long that I'm confident many testers use the latest master branch, 
> I'm reluctant to go through the hassle of cherry-picking commits...  
> and just release a minor release with all latest dev from master.
> 
> Call me lazy, but I'd rather keeping things simple here.

Maybe the development model followed by git itself would be a good
solution (merges instead of cherry-picking)? Although I fear org is a
much smaller project compared to git and it could be an overkill.

http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt

Hope this helps.

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2011-07-08 16:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 16:38 Thanks for Lilypond export (and minor comments) Torsten Anders
2011-07-07 20:01 ` Bastien
2011-07-08  1:35   ` Eric Schulte
2011-07-08  6:13     ` Bastien
2011-07-08  7:00       ` Nick Dokos
2011-07-08  9:08         ` Bastien
2011-07-08 16:02           ` Suvayu Ali [this message]
2011-07-09  8:44             ` Bastien
2011-07-10 16:50               ` Suvayu Ali
2011-07-11 16:50                 ` Bastien
2011-07-11 17:50                   ` suvayu ali
2011-07-19 12:29                   ` Bernt Hansen
2011-07-19 12:40                     ` suvayu ali
2011-07-08 21:00       ` Achim Gratz
2011-07-09  8:46         ` Bastien
2011-07-08  7:56     ` Martyn Jago

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=20110708180256.4d84bf95@kuru.homelinux.net \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=torsten.anders@beds.ac.uk \
    /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).