From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Gtk patch version 2, part 1
Date: Tue, 17 Dec 2002 20:22:15 +0100 (MET) [thread overview]
Message-ID: <200212172019.gBHKJN0U015894@stubby.bodenonline.com> (raw)
In-Reply-To: <buoznr59eim.fsf@mcspd15.ucom.lsi.nec.co.jp> from "Miles Bader" at dec 17, 2002 06:32:49
>
> BTW, unless you forsee massive future changes, why not check this stuff
> into CVS?
No, I hopefully will only do incremental changes from here on. The basic
structure should be OK.
I didn't want to check in so much before someone in the appropriate
position looked it over and gave the OK.
If nobody have objections I can check it in pretty much anytime.
> It seems like the only real pre-checkin change needed is ChangeLog
> entries (and that's pretty easy if you use Stefan's whizzy `C-x 4'-
> from-diff-mode feature).
Hmm, I didn't know about that. I'll be sure to try it.
Thanks,
Jan D.
next prev parent reply other threads:[~2002-12-17 19:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 20:22 Gtk patch version 2, part 1 Jan D.
2002-12-17 2:03 ` Miles Bader
2002-12-17 5:18 ` Eric Gillespie
2002-12-17 5:26 ` Eric Gillespie
2002-12-17 5:55 ` Miles Bader
2002-12-17 6:21 ` Eric Gillespie
2002-12-17 8:57 ` Miles Bader
2002-12-17 9:15 ` Miles Bader
2002-12-17 10:42 ` Eric Gillespie
2002-12-17 19:45 ` Jan D.
2002-12-18 2:01 ` Richard Stallman
2002-12-17 9:29 ` Eric Gillespie
2002-12-17 19:15 ` Jan D.
2002-12-17 9:32 ` Miles Bader
2002-12-17 19:22 ` Jan D. [this message]
2002-12-17 19:14 ` Jan D.
2002-12-18 1:08 ` Miles Bader
2002-12-18 6:40 ` Jan D.
2002-12-17 10:14 ` Simon Josefsson
2002-12-17 19:25 ` Jan D.
2002-12-18 0:50 ` Nick Roberts
2002-12-18 18:51 ` Richard Stallman
2002-12-17 18:44 ` Richard Stallman
2002-12-17 19:36 ` Jan D.
2002-12-18 5:54 ` Eli Zaretskii
2002-12-18 14:59 ` Alex Schroeder
2002-12-19 18:33 ` Richard Stallman
2002-12-20 15:21 ` Kai Großjohann
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=200212172019.gBHKJN0U015894@stubby.bodenonline.com \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@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).