From: Eli Zaretskii <eliz@gnu.org>
To: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
Cc: larsi@gnus.org, 37215-done@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#37215: [PATCH] vc-cvs-ignore writes absolute filenames and duplicate strings
Date: Sat, 22 Feb 2020 10:59:49 +0200 [thread overview]
Message-ID: <83tv3jhu9m.fsf@gnu.org> (raw)
In-Reply-To: <686a6419-308c-6536-3996-7f534ca19346@gmx.de> (message from Wolfgang Scherer on Fri, 21 Feb 2020 21:32:03 +0100)
> Cc: larsi@gnus.org, 37215@debbugs.gnu.org, dgutov@yandex.ru
> From: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
> Date: Fri, 21 Feb 2020 21:32:03 +0100
>
> > Please quote 'like this' in log messages, and try to avoid non-ASCII
> > characters there (they are generally only necessary in people's
> > names).
> OK
> >> +Patterns follow glob(7) syntax. Special characters \"?*[\\\" are
> >> +escaped with a backslash."
> > I'd say "should be escaped" here, since this is a requirement for the
> > argument passed to this function.
> Here is that amgbuity again ;-). It is only required, if the user
> wants a special character to match literally. It's perfectly fine to
> specify *.pyc as a pattern. I have phrased it like that.
> > Also, I'd mention that FILE can be a pattern, otherwise the reference
> > to patterns might come as a surprise to the reader.
> I emphasized more, that the basename of the FILE argument (not the
> entire FILE) is in fact a CVS ignore pattern.\x15\x04
> >> +to hear about anymore. If SORT is non-nil, sort the ines of the
> >> +ignore file." ^^^^
> > Typo: should be "lines".
> Right.
> >> + (goto-char (point-min))
> >> + (save-match-data
> >> + (unless (re-search-forward (concat "^" (regexp-quote str) "$") nil t)
> >> + (goto-char (point-max))
> > You could use non-nil, non-t 3rd argument of re-search-forward, in
> > which case the following goto-char would be redundant, right?
> Right, I just left the goto-char in there, because it makes it
> obvious what is going on. Switching to the side-effect optimization ...
Thanks, pushed to the release branch.
Please note that I need to make minor copyedits in the log message;
please try following this style in the future.
With this, I'm closing this bug report.
next prev parent reply other threads:[~2020-02-22 8:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 22:32 bug#37215: [PATCH] vc-cvs-ignore writes absolute filenames and duplicate strings Wolfgang Scherer
2019-09-15 13:12 ` Lars Ingebrigtsen
2020-01-05 3:59 ` Wolfgang Scherer
2020-01-22 12:43 ` Lars Ingebrigtsen
2020-01-30 19:44 ` Wolfgang Scherer
2020-02-13 19:36 ` Eli Zaretskii
2020-02-14 1:24 ` Wolfgang Scherer
2020-02-14 8:33 ` Eli Zaretskii
2020-02-15 1:42 ` Wolfgang Scherer
2020-02-15 7:44 ` Eli Zaretskii
2020-02-15 12:55 ` Dmitry Gutov
2020-02-19 23:02 ` Wolfgang Scherer
2020-02-16 0:20 ` Wolfgang Scherer
2020-02-19 23:06 ` Wolfgang Scherer
2020-02-21 9:31 ` Eli Zaretskii
2020-02-21 10:16 ` Dmitry Gutov
2020-02-21 20:44 ` Wolfgang Scherer
2020-02-21 21:30 ` Dmitry Gutov
2020-02-21 22:23 ` Wolfgang Scherer
2020-02-21 20:32 ` Wolfgang Scherer
2020-02-22 8:59 ` Eli Zaretskii [this message]
2020-02-14 2:50 ` Wolfgang Scherer
2020-02-14 8:39 ` Eli Zaretskii
2020-02-14 9:24 ` Eli Zaretskii
2020-02-28 16:07 ` Mattias Engdegård
2020-02-28 16:24 ` Eli Zaretskii
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=83tv3jhu9m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37215-done@debbugs.gnu.org \
--cc=Wolfgang.Scherer@gmx.de \
--cc=dgutov@yandex.ru \
--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).