all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: SOLVED
Date: Thu, 05 May 2016 21:33:11 +0000	[thread overview]
Message-ID: <CAFyQvY1h+42ZAga0+AzV9_vPcn5w9B5+kbOYYQf-NN3OGqcS7A@mail.gmail.com> (raw)
In-Reply-To: <877ff8cjqg.fsf@mat.ucm.es>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Hi Uwe,

I am using Google Inbox to write emails. I apologize for the email format
as I don't know what I can do to fix this. This is what it looks like to me
when I am writing the email: http://i.imgur.com/oYhaTHg.png


> I just followed your instructions of your other mail to rebase to
> emacs-25, but Daniels changes are not there.
>


> His changes seem only to be in emacs-master. (I am sorry I am not very
> familiar with git, for my personal stuff I use hg and I use even the
> git-hg plugin to maintain matlab, but I don't dare to do that for
> emacs...)
>

Sorry for creating this confusion. You are correct; those changes to vc-hg
(
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=de76a167dc09dc695a5acebabb7ab354a6bf556e
)
are only in the master branch. So there is no point sending a patch rebased
to emasc-25. I had incorrectly assumed that your documentation patch could
apply to emacs-25 too.

So just rebase to the master branch using the below.

git fetch --all
git checkout master
git reset --hard origin/master

Then format your patch and send it to bug-gnu-emacs@gnu.org.
-- 

-- 
Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1881 bytes --]

  reply	other threads:[~2016-05-05 21:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 20:01 vc-hg modeline changed Uwe Brauer
2016-05-05  9:15 ` SOLVED (was: vc-hg modeline changed.) Uwe Brauer
2016-05-05 11:26   ` Kaushal Modi
2016-05-05 16:10     ` SOLVED Uwe Brauer
2016-05-05 16:18       ` SOLVED Kaushal Modi
2016-05-05 16:41         ` SOLVED Andreas Schwab
2016-05-05 20:12     ` SOLVED Uwe Brauer
2016-05-06  6:27       ` SOLVED Eli Zaretskii
2016-05-05 20:50     ` SOLVED Uwe Brauer
2016-05-05 21:33       ` Kaushal Modi [this message]
2016-05-06  7:53         ` SOLVED Uwe Brauer
2016-05-06  9:28           ` SOLVED Yuri Khan
2016-05-06 10:29             ` SOLVED Uwe Brauer
2016-05-06 10:45             ` SOLVED II (was: SOLVED) Uwe Brauer
2016-05-06 12:10             ` SOLVED Clément Pit--Claudel
2016-05-06 12:24               ` SOLVED Yuri Khan
2016-05-06 12:32                 ` SOLVED Clément Pit--Claudel
2016-05-06 13:00                   ` SOLVED Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2012-01-28 20:20 Xemacs: org-preview-latex-fragment, png not readable Uwe Brauer
2012-01-28 20:59 ` Solved (was: Xemacs: org-preview-latex-fragment, png not readable.) Uwe Brauer
2012-01-28 22:33   ` Solved Bastien
2012-01-29  0:13     ` Solved Nick Dokos

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

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

  git send-email \
    --in-reply-to=CAFyQvY1h+42ZAga0+AzV9_vPcn5w9B5+kbOYYQf-NN3OGqcS7A@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.