From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: pop3.el itegration with netrc.el
Date: 18 Oct 2004 14:30:49 -0400 [thread overview]
Message-ID: <4nis97ubdy.fsf@lifelogs.com> (raw)
In-Reply-To: <87hdotx7it.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "Mon, 18 Oct 2004 08:13:46 +0900")
On Mon, 18 Oct 2004, miles@gnu.org wrote:
> The main problem is ChangeLogs: if you add entries to lisp/ChangeLog
> (in Gnus) or lisp/gnus/ChangeLog (in Emacs), it's clear that they should
> simply be propagated to the corresponding file in the other tree,
> because the changes they describe almost certainly will be as well.
>
> However, if files from Gnus are present in other Emacs directories, then
> this easy 1-to-1 correspondence is lost, so it will likely require me to
> manually deal with such ChangeLog entries. This problem already exists
> with texi/ChangeLog, but it's not that heavily updated, so it hasn't
> proved much of burden; hopefully the bulk of Gnus changes will still
> remain inside the main gnus source even if these "generic" files are
> moved.
>
> But anyway, dealing with ChangeLogs is a relatively minor hassle becuase
> it's only 1 or 2 files, and if it gets too annoying I'll write a script
> that deals with it.
If you could make the default add-change-log-entry-other-window to
mention the arch-tag (if available at the end of the file), I think
your life and ours will be much easier. This would require changes to
add-log.el though.
I love the idea of a general identifier for all files in the VCS.
That makes the CVS annoyance of directory mis-management much easier
to reconcile with TLA. Thanks for helping with all the Gnus <-> Emacs
sync issues.
Ted
next prev parent reply other threads:[~2004-10-18 18:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 15:44 Ted Zlatanov
2004-10-14 18:21 ` Simon Josefsson
2004-10-14 18:37 ` Ted Zlatanov
2004-10-14 18:56 ` Simon Josefsson
2004-10-14 18:49 ` Reiner Steib
2004-10-14 19:01 ` Simon Josefsson
2004-10-14 19:52 ` Reiner Steib
2004-10-14 22:39 ` Simon Josefsson
2004-10-15 17:08 ` Ted Zlatanov
2004-10-15 17:43 ` Simon Josefsson
2004-10-15 19:07 ` Ted Zlatanov
2004-10-15 19:16 ` Reiner Steib
2004-10-17 23:13 ` Miles Bader
2004-10-18 18:30 ` Ted Zlatanov [this message]
2004-10-21 18:35 ` Ted Zlatanov
2004-10-15 18:07 ` Reiner Steib
2004-10-15 19:14 ` encrypt.el (was: pop3.el itegration with netrc.el) Ted Zlatanov
[not found] ` <iluwtxrvkfb.fsf@latte.josefsson.org>
[not found] ` <E1CIozF-00034v-V7@fencepost.gnu.org>
[not found] ` <4n4qkrvrwu.fsf@lifelogs.com>
[not found] ` <E1CJx6h-0000Ns-QW@fencepost.gnu.org>
[not found] ` <4nsm87vrgk.fsf@lifelogs.com>
[not found] ` <4nr7m9j1ah.fsf@lifelogs.com>
2004-12-01 22:12 ` encrypt.el Reiner Steib
2004-12-02 16:36 ` encrypt.el Ted Zlatanov
2004-12-02 20:56 ` encrypt.el Reiner Steib
2004-12-07 17:50 ` encrypt.el Ted Zlatanov
2004-10-15 17:48 ` pop3.el itegration with netrc.el Reiner Steib
2004-10-15 17:58 ` Simon Josefsson
2004-10-15 18:55 ` Reiner Steib
2004-10-17 23:22 ` Miles Bader
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=4nis97ubdy.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).