From: "Gustav Hållberg" <gustav@gmail.com>
To: git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>
Cc: "David Kågedal" <davidk@lysator.liu.se>
Subject: [StGit] Emacs mode merge request
Date: Wed, 9 Jun 2010 14:11:25 +0200 [thread overview]
Message-ID: <AANLkTiklRA-d8p3NhpvjZLua0zE7uK8RFrJTegCr-Jjd@mail.gmail.com> (raw)
Catalin, can you please merge the following series from
git://github.com/gustavh/stgit.git "proposed" branch.
All the patches are small, incremental improvements and bug fixes to
the Emacs mode.
199cec3 tutorial: Very minor typo fixes in the Emacs section
939ff13 stgit.el: Add stgit-{git,stg}-program variables
e23eb46 stgit.el: Rearrange customizations a bit
5be0bca stgit.el: Add "Customize StGit" menu entry
cde79c7 stgit.el: Improve how "t h" mode finds old commits
160b5bf stgit.el: Make C-{up,down} move between groups of patches
b8738ed stgit.el: Add a few links to some customization variables
d528462 stgit.el: Repair ! for historical commits
16e96c0 stgit.el: Honor stgit-find-copies-harder in stgit-diff-range
65f3ffa stgit.el: Honor stgit-find-copies-harder when showing entire patches
108e5c8 stgit.el: Fix showing diff in file that has been both copied
and modified
The branch is based on your "proposed" branch (53055a56).
Somewhat unrelated, whom should I talk to about getting the Emacs mode
into the Debian package?
I think the Emacs mode ought to go into the 'stgit' package rather
than 'stgit-contrib', but some may disagree...
Thanks,
Gustav
next reply other threads:[~2010-06-09 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 12:11 Gustav Hållberg [this message]
2010-06-09 15:30 ` [StGit] Emacs mode merge request Gustav Hållberg
2010-06-10 7:31 ` Gustav Hållberg
2010-06-16 9:06 ` Catalin Marinas
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=AANLkTiklRA-d8p3NhpvjZLua0zE7uK8RFrJTegCr-Jjd@mail.gmail.com \
--to=gustav@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).