public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Emacs is coming back - please test
Date: Tue, 10 Jul 2007 11:45:00 -0000	[thread overview]
Message-ID: <20070710114508.GB10945@calimero.vinschen.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707101121010.15358@recycler.in-berlin.de>

On Jul 10 11:24, Steffen Sledz wrote:
> On Tue, 10 Jul 2007, Dr. Volker Zell wrote:
> > I splitted out the following conflicting files from my xemacs package:
> 
> What's the right way to handle such conflicts?
> 
> > 
> > xemacs-tags:            (conflicts with ctags-5.6 and now with upcoming emacs-22.1)
> >   usr/bin/ctags.exe
> >   usr/bin/etags.exe
> >   usr/share/man/man1/ctags.1.gz
> >   usr/share/man/man1/etags.1.gz
> 
> Exclude from emacs and make ctags a requirement?

Exclude, yes.  A requirement, no.  ctags/etags are no requirement
to edit files.

> 
> > xemacs-emacs-common:    (used to conflict with emacs-21.2 now with upcoming emacs-22.1)
> >   /usr/bin/b2m.exe
> >   /usr/bin/rcs-checkin
> 
> No idea.

That's one between Volker and you.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  reply	other threads:[~2007-07-10 11:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 22:24 Steffen Sledz
2007-07-09 12:16 ` Eric Blake
2007-07-09 12:35   ` Steffen Sledz
2007-07-15 12:23   ` Steffen Sledz
2007-07-09 12:41 ` Eric Blake
2007-07-15 18:30   ` Steffen Sledz
2007-07-10  8:36 ` Dr. Volker Zell
2007-07-10  9:24   ` Steffen Sledz
2007-07-10 11:45     ` Corinna Vinschen [this message]
2007-07-10 16:23       ` Dr. Volker Zell
2007-07-10 16:45         ` Corinna Vinschen
2007-07-10 17:56       ` Steffen Sledz
2007-07-11 21:30         ` Reini Urban
2007-07-19 19:15 idirectscm

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=20070710114508.GB10945@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).