emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Fix the single quote printed in the message printed by org-table-edit-formulas
Date: Fri, 11 Mar 2016 13:47:45 -0500	[thread overview]
Message-ID: <877fh8yhpq.fsf@kyleam.com> (raw)
In-Reply-To: <CAFyQvY0c8NFZBiYx9a3MQj2t_r2S2f1eyKow8wy8kmmb_ifV4g@mail.gmail.com> (Kaushal Modi's message of "Fri, 11 Mar 2016 12:44:48 -0500")

Kaushal Modi <kaushal.modi@gmail.com> writes:

> Patch (after rebasing to 5a735b0) attached. I hope it works.

Thanks.  It almost works :)

Applying the patch fails because there's a whitespace change in one of
the context lines (the first one above the org-table-align change).  You
should be able to see the same failure on your end if you make a test
branch off of maint and then try to apply your patch.  But the patch
applies fine with the --ignore-whitespace flag to git am, so there is no
need to resend it.

I'll have another look at the changes tonight and will push it then
unless there are more comments from me or others.

> Git newbie question:
>
> Making the changes in the maint version of these 4 files manually was a bit
> of a pain. What's the right way of porting changes from one branch to
> another?

You can rebase the patch branch from master to maint.  From Magit, you
can use the magit-rebase-subset command ("rs").  From the command line,
you could do something like

    git rebase --onto maint master <patch-branch>

Since in this case the branch only consists of one commit, you could
also just make a new branch off of maint and cherry pick the commit from
the original branch.

In either case, Git will let you know if there are any conflicts you
need to resolve.

> I am curious how the changes will be ported from the maint branch
> to the master branch.

I'll merge maint into master.

--
Kyle

  reply	other threads:[~2016-03-11 18:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 16:18 [PATCH] Fix the single quote printed in the message printed by org-table-edit-formulas Kaushal Modi
2016-03-10  9:25 ` Nicolas Goaziou
2016-03-10 15:33   ` Kaushal Modi
2016-03-10 16:05     ` Paul Eggert
2016-03-10 16:00   ` Kyle Meyer
2016-03-10 16:38 ` Kyle Meyer
2016-03-10 16:41   ` Kaushal Modi
2016-03-10 17:47     ` Kaushal Modi
2016-03-10 18:24       ` Kaushal Modi
2016-03-11  1:39       ` Paul Eggert
2016-03-11  3:22         ` Kaushal Modi
2016-03-11  4:30           ` Kyle Meyer
2016-03-11  4:55             ` Kaushal Modi
2016-03-11  5:12               ` Kyle Meyer
2016-03-11 17:44                 ` Kaushal Modi
2016-03-11 18:47                   ` Kyle Meyer [this message]
2016-03-11 19:16                     ` Kyle Meyer
2016-03-12  4:01                     ` Kyle Meyer
2016-03-12  4:57                       ` Kaushal Modi

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=877fh8yhpq.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    /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).