all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33476@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#33476: [PATCH] Fix occur revert with list-matching-lines-jump-to-current-line
Date: Tue, 11 Dec 2018 18:07:52 -0500	[thread overview]
Message-ID: <d636r33bnb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83efap3nii.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Dec 2018 08:27:01 +0200")

Eli Zaretskii wrote:

> Please don't use the instructions in admin/notes/repo

They just happened to get outdated in this one specific area
({bzr,git}merge.el used to skip anything matching "merge",
but that was found to be too broad).

> use the instructions in CONTRIBUTE instead. Personally, I'm not sure
> why the former exists

I view(ed) it as:

CONTRIBUTE is for people without write access
admin/notes/repo is for people with write access

Obviously these can get a bit blurred with distributed VCS, but not totally.
Duplication of information should of course be avoided.





  parent reply	other threads:[~2018-12-11 23:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 21:10 bug#33476: [PATCH] Fix occur revert with list-matching-lines-jump-to-current-line Raimon Grau
2018-11-24 21:54 ` Juri Linkov
2018-11-26 17:54   ` Eli Zaretskii
2018-12-08  9:25   ` Eli Zaretskii
2018-12-08 23:16     ` Juri Linkov
2018-12-09  7:55       ` Eli Zaretskii
2018-12-09 23:54         ` Juri Linkov
2018-12-10  6:27           ` Eli Zaretskii
2018-12-11  4:40             ` Richard Stallman
2018-12-11 23:07             ` Glenn Morris [this message]
2018-12-12 17:07               ` Eli Zaretskii
2018-12-13  0:12               ` Richard Stallman
2018-12-13  8:57                 ` Robert Pluim
2018-12-13 21:14                   ` Richard Stallman

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=d636r33bnb.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33476@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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.