emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Achim Gratz <Stromeko-i47jiTeKxPI@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Missing patch from Eric Schulte from 2013-10-09
Date: Tue, 07 Jan 2014 13:58:09 +0100	[thread overview]
Message-ID: <87zjn8osny.fsf@somewhere.org> (raw)
In-Reply-To: <8761px9cwz.fsf-9O0xPIFIXLULmYpASZe/Uw@public.gmane.org> (Achim Gratz's message of "Mon, 06 Jan 2014 19:35:08 +0100")

Hi Achim,

> The maint branch contains the release (8.2.4 for your example) plus
> those patches that are purely bugfixes (i.e. do not alter, remove or
> introduce features).  In your example, eight such patches had
> accumulated, placing you at commit f1b933: release_8.2.4-8-gf1b9339.
>
> The master branch includes everything on maint plus any patches that
> alter, remove or introduce features.  That amounted to 350 commits past
> the 8.2.4 release at the merge into master (d55f06), including those
> eight from maint: release_8.2.4-350-gd55f063.

Thanks a lot for these clear explanations.

If I understand well, to find patches from the master branch in the
maint branch, I'll need to wait until the next major release, i.e.
release 8.3. Am I right?

Regards,
 Francesco

      parent reply	other threads:[~2014-01-07 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 12:28 Missing patch from Eric Schulte from 2013-10-09 Francesco Pizzolante
2013-12-22  8:46 ` Bastien
     [not found]   ` <87txe18e95.fsf-E3UqQZAQFPqWIDz0JBNUog@public.gmane.org>
2014-01-06 14:54     ` Francesco Pizzolante
2014-01-06 18:35       ` Achim Gratz
     [not found]         ` <8761px9cwz.fsf-9O0xPIFIXLULmYpASZe/Uw@public.gmane.org>
2014-01-07 12:58           ` Francesco Pizzolante [this message]

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=87zjn8osny.fsf@somewhere.org \
    --to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
    --cc=Stromeko-i47jiTeKxPI@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).