From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Invalid function: with-parsed-tramp-file-name with Perl
Date: Sat, 22 Sep 2012 09:03:30 +0200 [thread overview]
Message-ID: <87r4pufsjh.fsf@Rainer.invalid> (raw)
In-Reply-To: 87mx0izgrx.fsf@bzg.ath.cx
Bastien writes:
> Can you summarize what would be the change and why it is called for?
The tag release_7.8.11 is affixed to the merge commit, which means that
it's first parent is on the master branch rather than maint. The change
sets it back one commit so that it correctly is located on the maint
branch.
We'll have to tell users to forcibly update the tags again.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2012-09-22 7:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 5:05 Invalid function: with-parsed-tramp-file-name with Perl Nick Dokos
2012-09-22 6:41 ` Achim Gratz
2012-09-22 6:57 ` Bastien
2012-09-22 7:03 ` Achim Gratz [this message]
2012-09-22 8:19 ` Bastien
2012-09-22 11:57 ` Achim Gratz
2012-09-22 16:14 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 11:54 Loris Bennett
2012-06-21 13:53 ` Nick Dokos
2012-06-21 14:51 ` Loris Bennett
2012-06-21 15:13 ` Nick Dokos
2012-06-25 7:05 ` Loris Bennett
2012-09-18 14:04 ` Loris Bennett
2012-09-19 7:45 ` Bastien
2012-09-19 9:28 ` Loris Bennett
2012-09-19 9:59 ` Bastien
2012-09-19 10:29 ` Loris Bennett
2012-09-19 13:49 ` Nick Dokos
2012-09-19 18:52 ` Achim Gratz
2012-09-19 19:51 ` Nick Dokos
2012-09-20 14:12 ` Loris Bennett
2012-09-20 15:11 ` Nick Dokos
2012-09-20 15:30 ` Nick Dokos
2012-09-20 17:21 ` Nick Dokos
2012-09-20 17:36 ` Nick Dokos
2012-09-20 18:29 ` Eric Schulte
2012-09-20 19:18 ` Achim Gratz
2012-09-20 20:51 ` Nick Dokos
2012-09-20 21:00 ` Achim Gratz
2012-09-20 22:26 ` Nick Dokos
2012-09-21 17:49 ` Achim Gratz
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=87r4pufsjh.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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 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).