unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>,
	Dan Nicolaescu <dann@ics.uci.edu>,
	emacs-devel@gnu.org
Subject: Re: Option to customize the -m message flag of cvs?
Date: Tue, 6 Jan 2009 21:21:16 +0100	[thread overview]
Message-ID: <f7ccd24b0901061221g61ad6246sa0505551381a349f@mail.gmail.com> (raw)
In-Reply-To: <jwvtz8cmh0d.fsf-monnier+emacs@gnu.org>

On Tue, Jan 6, 2009 at 19:26, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> I don't know about "strongly" but I tend to agree: -m is the right
> option to use, and if it inserts advertisement, well, that's on purpose,
> so it's a feature rather than a bug.

I understand that to mean that it's not a problem if I simply continue
using CVSNT and the advertisements go into the Emacs CVS logs.

> PS: We could go one step further and automatically detect that it's
> CVSNT and it supports -M and automatically use -M over -m, thus
> defeating CVSNT's advertisement.  But this may simply lead to CVSNT
> using some other means of getting its advertisement message in some
> future version.

It's the CVSNT people who added -M and explained it's use. They have a
FAQ about how to avoid the message, both in the client and the CVSNT
server; they even distribute (or are going to) a custom TortoiseCVS
that already uses -M. This is not a war, just a way (misguided or not)
of increasing visibility for their chosen business model.

    Juanma




  reply	other threads:[~2009-01-06 20:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 12:58 Option to customize the -m message flag of cvs? Juanma Barranquero
2008-12-29 17:10 ` martin rudalics
2008-12-29 19:14   ` Eli Zaretskii
2008-12-29 19:57     ` Juanma Barranquero
2008-12-29 20:52       ` Eli Zaretskii
2008-12-29 21:18         ` martin rudalics
2008-12-30  4:04           ` Eli Zaretskii
2008-12-30  7:26             ` martin rudalics
2008-12-30 22:05               ` Eli Zaretskii
2008-12-31  9:15                 ` martin rudalics
2008-12-31 19:14                   ` Eli Zaretskii
2008-12-31 21:28                     ` martin rudalics
2009-01-06 10:57                     ` martin rudalics
2009-01-06 16:08                       ` Dan Nicolaescu
2009-01-06 17:06                         ` Juanma Barranquero
2009-01-06 20:49                           ` Eli Zaretskii
2009-01-06 20:59                             ` Juanma Barranquero
2009-01-06 21:10                               ` Eli Zaretskii
2009-01-07  8:18                             ` martin rudalics
2009-01-07 21:21                               ` Eli Zaretskii
2009-01-06 18:26                         ` Stefan Monnier
2009-01-06 20:21                           ` Juanma Barranquero [this message]
2009-01-12 22:18                           ` Sam Steingold
2009-01-12 23:52                             ` Juanma Barranquero
2009-01-13  1:57                               ` dhruva
2009-01-13  1:59                                 ` dhruva
2009-01-13 18:51                               ` Sam Steingold
2009-01-13 21:20                                 ` Juanma Barranquero
2009-01-06 22:32                         ` mail
2009-01-07  8:52                           ` Juanma Barranquero
2009-01-06 20:46                       ` Eli Zaretskii
2009-01-06 20:53                         ` Juanma Barranquero
2009-01-06 21:01                           ` Eli Zaretskii
2009-01-06 21:06                             ` Juanma Barranquero
2009-01-06 21:14                               ` Eli Zaretskii
2009-01-06 21:24                                 ` Juanma Barranquero
2009-01-06 21:35                           ` Stefan Monnier
2008-12-29 23:29         ` Juanma Barranquero
2008-12-30  9:34         ` Juanma Barranquero

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=f7ccd24b0901061221g61ad6246sa0505551381a349f@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=dann@ics.uci.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rudalics@gmx.at \
    /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).