From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>,
Juri Linkov <juri@linkov.net>
Subject: Re: Organizing the NEWS file a bit better
Date: Mon, 6 Sep 2021 22:38:16 +0200 [thread overview]
Message-ID: <CADwFkm=opQyMdoghQveNKPhaxHeC=XyLhV0Hf9eKrx8X8LXWQA@mail.gmail.com> (raw)
In-Reply-To: <83bl55qzqz.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> It doesn't break it for me (though I don't think I understand what you
> are describing: the archeology on the branch and on master are
> separate and independent).
OK, so let's stick to master. It's a known limitation in git that it
is hard to access after the file was moved. Maybe I don't understand
what you're saying, but this limitation in git is exactly why we are
avoiding moving files in the first place.
Could you explain how you carry out archeology on etc/NEWS.27? How do
I find out who introduced this line:
** Emacs now uses GMP, the GNU Multiple Precision library.
?
> vc-region-history builds _upon_ annotate, and saves you the trouble of
> invoking annotate many times, each time specifying the commit SHA.
I haven't ever had to specify a commit SHA with vc-annotate.
By the way, I realize I was being unfair to vc-annotate. There are in
fact a number of commands that make going through history very
convenient, such as vc-annotate-next-revision,
vc-annotate-prev-revision, and vc-annotate-revision-at-line.
next prev parent reply other threads:[~2021-09-06 20:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:53 Organizing the NEWS file a bit better Stefan Kangas
2021-09-04 19:04 ` Lars Ingebrigtsen
2021-09-04 19:34 ` Stefan Kangas
2021-09-04 19:47 ` Eli Zaretskii
2021-09-04 20:36 ` Tim Cross
2021-09-04 21:08 ` Stefan Kangas
2021-09-06 2:30 ` Stefan Kangas
2021-09-06 3:45 ` Jean-Christophe Helary
2021-09-06 6:35 ` Juri Linkov
2021-09-06 6:57 ` Stefan Kangas
2021-09-06 8:37 ` Lars Ingebrigtsen
2021-09-06 9:01 ` Stefan Kangas
2021-09-06 9:04 ` Lars Ingebrigtsen
2021-09-06 18:17 ` Stefan Kangas
2021-09-06 18:42 ` Eli Zaretskii
2021-09-06 18:57 ` Stefan Kangas
2021-09-06 19:18 ` Eli Zaretskii
2021-09-06 20:38 ` Stefan Kangas [this message]
2021-09-06 20:42 ` Stefan Kangas
2021-09-07 5:38 ` Eli Zaretskii
2021-09-07 6:47 ` Stefan Kangas
2021-09-07 6:53 ` Stefan Kangas
2021-09-07 8:12 ` Eli Zaretskii
2021-09-07 15:09 ` Lars Ingebrigtsen
2021-09-06 11:01 ` Eli Zaretskii
2021-09-06 11:07 ` Lars Ingebrigtsen
2021-09-06 11:20 ` Eli Zaretskii
2021-09-06 10:39 ` Eli Zaretskii
2021-09-06 10:14 ` Eli Zaretskii
2021-09-04 19:05 ` Juri Linkov
2021-09-04 19:16 ` Eli Zaretskii
2021-09-04 19:35 ` Stefan Kangas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=opQyMdoghQveNKPhaxHeC=XyLhV0Hf9eKrx8X8LXWQA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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.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).