all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Option to customize the -m message flag of cvs?
Date: Wed, 07 Jan 2009 23:21:25 +0200	[thread overview]
Message-ID: <u3afulsmi.fsf@gnu.org> (raw)
In-Reply-To: <4964656F.20001@gmx.at>

> Date: Wed, 07 Jan 2009 09:18:55 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
> 
>  > Is the vc-dir and "cvs -f status" problem the only reason why you
>  > cannot switch to the recent port of CVS offered by
>  > http://ftp.gnu.org/non-gnu/cvs/binary/ ?  If there are other reasons,
>  > what are they?
> 
> The "cvs -f status" problem is an initial obstacle.  I don't have the
> slightest idea what other problems I might encounter when using that
> port.

There's no need to assume there will be other problems, without trying
it first.  Can you try and see how well it goes?

> Currently, I'm mostly harassed by the problems that
> 
> (1) reverting a buffer under VC may change its line endings from Unix
>      to DOS, and
> 
> (2) `vc-diff' gets me a Diff buffer with ^M appended on each line.

These two sound unrelated to vc-dir (or even VC in general), but
rather bugs related to setting up the encoding/decoding stuff when
these commands run.

> In the future, I'll be more prudent when reading text like
> 
>       Hmmm, so all the more reason for people to stop committing stuff
>       separately... :-/
> 
>       -Miles

Yes, people who live on GNU/Linux exclusively frequently underestimate
the plight of using their recipes on other platforms.




  reply	other threads:[~2009-01-07 21: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 [this message]
2009-01-06 18:26                         ` Stefan Monnier
2009-01-06 20:21                           ` Juanma Barranquero
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u3afulsmi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 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.