unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bill Meier <wmeier@newsguy.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: [PATCH] nt/gmake,defs, nt/nmake.defs
Date: Fri, 18 Jan 2008 19:06:16 +0200	[thread overview]
Message-ID: <u63xroygn.fsf@gnu.org> (raw)
In-Reply-To: <loom.20080118T160505-186@post.gmane.org> (message from Bill Meier on Fri, 18 Jan 2008 16:14:43 +0000 (UTC))

> From: Bill Meier <wmeier@newsguy.com>
> Date: Fri, 18 Jan 2008 16:14:43 +0000 (UTC)
> 
> Should I diff the patch against EMACS_22_BASE ?  MAIN (HEAD) ? or both ?

It's better to diff against the EMACS_22_BASE branch: it will make
sure the change will be in the next release 22.2, and it will be
automatically merged into the trunk anyway.

> (Is it something like bug fixes to EMACS_22_BASE and enhancements to MAIN ?)

Yes, but yours is a bug report, not a request for enhancement.

But please do try to make your changes as isolated and unintrusive as
possible, because our reluctance to make dangerous changes in the
release branch.

Thanks for working on this.




  reply	other threads:[~2008-01-18 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 22:18 [PATCH] nt/gmake,defs, nt/nmake.defs Bill Meier
2008-01-16 19:17 ` Eli Zaretskii
2008-01-18 16:14   ` Bill Meier
2008-01-18 17:06     ` Eli Zaretskii [this message]
2008-01-18 21:16       ` Eli Zaretskii
2008-01-18 21:41       ` Jason Rumney
2008-01-19  8:52         ` Eli Zaretskii
2008-01-19 10:53           ` Jason Rumney
2008-01-19 21:24             ` Bill Meier
2008-01-19 22:01               ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2008-01-20 17:35 Bill Meier
2008-01-20 17:55 ` Bill Meier

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=u63xroygn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=wmeier@newsguy.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. 
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).