From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com, Torsten Anders <torsten.anders@beds.ac.uk>,
emacs-orgmode@gnu.org
Subject: Re: Thanks for Lilypond export (and minor comments)
Date: Fri, 08 Jul 2011 03:00:24 -0400 [thread overview]
Message-ID: <17595.1310108424@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bastien <bzg@altern.org> of "Fri, 08 Jul 2011 08:13:06 +0200." <87oc15nvv1.fsf@gnu.org>
Bastien <bzg@altern.org> wrote:
> > is there a process for bug-fix commits like this one which should be
> > pushed through to Emacs24? I'm thinking a branch (maintenance?) to
> > which this should be pushed or a special way to tag the commit?
>
> there is none for now -- I need to think about it.
>
> As I will need a few hours more to create the ChangeLog between 7.5
> and 7.6 for Emacs (yeah!), I plan to make a minor release 7.6.1 that
> will be the one we'll have in Emacs. Probably tomorrow morning or
> sunday morning.
>
> So this fix will go thru Emacs, then we can think about a better
> process. Detailed suggestions from git power users welcome!
>
I'm not sure whether I posted this before but if you haven't seen
it before, it's probably worth reading:
http://nvie.com/posts/a-successful-git-branching-model/
There is a set of tools that supports this kind of workflow at
https://github.com/nvie/gitflow
Nick
next prev parent reply other threads:[~2011-07-08 7:00 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 [this message]
2011-07-08 9:08 ` Bastien
2011-07-08 16:02 ` Suvayu Ali
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=17595.1310108424@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--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).