unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Miles Bader" <miles@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: linum.el?
Date: Wed, 30 Jan 2008 22:27:29 +0100	[thread overview]
Message-ID: <f7ccd24b0801301327s335cf91dy435960c7d838c3db@mail.gmail.com> (raw)
In-Reply-To: <87d4rj58r0.fsf@catnip.gol.com>

On Jan 30, 2008 10:00 PM, Miles Bader <miles@gnu.org> wrote:

> I've found that even "modular" new features can be pretty annoying in
> merging to the trunk -- even if they start out the same on both the
> trunk and branch, many files seem to nevertheless generate a lot of
> merge conflicts.

Miles, I know you shoulder most, if not all, the work in merging the
branches and the trunk, so I understand you position.

But the criteria for whether a package belongs to the release branch
or not should be mostly about its readiness and general usefulness.
How difficult is to maintain the branches synchronized it's IMHO
secondary (*only* as a criterion for inclusion, I hasten to repeat;
I'm not slighting you or the work you do).

That said, in the particular case of linum.el I don't have a strong
opinion for or against it being in 22.2. I find it useful and stable,
but I don't know if it is generally useful enough to merit increasing
your workload.

             Juanma




  reply	other threads:[~2008-01-30 21:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31  9:40 linum.el? Juanma Barranquero
2007-10-31 15:47 ` linum.el? Stefan Monnier
2007-10-31 23:58 ` linum.el? Richard Stallman
2007-11-01  1:39   ` linum.el? Juanma Barranquero
     [not found]     ` <E1J6Y7I-0002zs-C9@fencepost.gnu.org>
2007-12-26 16:09       ` linum.el? Markus Triska
2007-12-26 23:28         ` linum.el? Stefan Monnier
2007-12-27  0:06           ` linum.el? Juanma Barranquero
2007-12-27 18:24             ` linum.el? Richard Stallman
2008-01-20 23:50               ` linum.el? Juanma Barranquero
2008-01-30  2:07                 ` linum.el? Juanma Barranquero
2008-01-30  3:03                   ` linum.el? Miles Bader
2008-01-30  3:18                     ` linum.el? Juanma Barranquero
2008-01-30 13:25                       ` linum.el? Miles Bader
2008-01-30 14:53                         ` linum.el? Juanma Barranquero
2008-01-30 17:01                           ` linum.el? Miles Bader
2008-01-30 20:52                       ` linum.el? Richard Stallman
2008-01-30 21:00                         ` linum.el? Miles Bader
2008-01-30 21:27                           ` Juanma Barranquero [this message]
2008-01-30 22:13                             ` linum.el? Miles Bader
2008-01-30 22:33                               ` linum.el? Juanma Barranquero
2008-01-31 18:51                           ` linum.el? Richard Stallman
2008-01-31 22:05                             ` linum.el? Miles Bader
2007-12-29  7:22             ` linum.el? Stefan Monnier
2007-12-27 18:24           ` linum.el? Richard Stallman
2007-12-29  7:26             ` linum.el? Stefan Monnier
2007-12-29 17:48               ` linum.el? Richard Stallman
2008-01-02  2:12                 ` linum.el? Stefan Monnier
2008-01-03  9:50                   ` linum.el? Richard Stallman
2007-12-27 13:42         ` linum.el? Richard Stallman
2007-12-27 19:18           ` linum.el? Markus Triska
2007-12-28 13:55             ` linum.el? Richard Stallman
2007-12-28 20:22               ` linum.el? Markus Triska
2007-12-29  7:31                 ` linum.el? Stefan Monnier
2007-12-29 13:51                 ` linum.el? Richard Stallman
2007-11-13 17:28 ` linum.el? 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=f7ccd24b0801301327s335cf91dy435960c7d838c3db@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@gnu.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).