From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: expire-by-2010-02-18@kanis.fr, emacs-devel@gnu.org
Subject: Re: ja-dic.el and SKK-JYSYO.L
Date: Wed, 17 Feb 2010 15:26:17 +0900 [thread overview]
Message-ID: <tl7mxz8qsxi.fsf@m17n.org> (raw)
In-Reply-To: <jwvaav8ieb1.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 17 Feb 2010 01:11:32 -0500)
In article <jwvaav8ieb1.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>>> If we do that, we need to replace the file by a URL in the tarball (so
>>>>> the file in `admin' is just a cache).
>>> > ?? I don't understand exactly what you mean.
>>> It's because I was vague: the precise way we replace the file by a URL
>>> is left unspecified.
> > How about including .bzr directory (or something) so that a
> > user who extracted files from the tarball can get all files
> > just by typing "bzr up" under admin/*? Is such a thing
> > possible by bzr?
> It'd have to be "bzr revert" rather than "bzr update" since missing
> files are considered as implicit "bzr rm" requests.
Ah, I see.
> I'd rather have a plain file giving URLs (and md5sums) so people who
> want to get the source will know where to find it.
URLs change from time to time and are not reliable. I think
it is better that we keep the copies by ourselves in the bzr
repository or some of FSF's ftp site. I think the bzr
repository is better because it is appearent to users when
we update files.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-02-17 6:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 9:47 ja-dic.el and SKK-JYSYO.L Ivan Kanis
2010-02-12 10:15 ` Eli Zaretskii
2010-02-12 12:44 ` Kenichi Handa
2010-02-13 10:42 ` Ivan Kanis
2010-02-16 7:51 ` Kenichi Handa
2010-02-16 14:04 ` Stefan Monnier
2010-02-17 1:01 ` Kenichi Handa
2010-02-17 1:46 ` Stefan Monnier
2010-02-17 5:29 ` Kenichi Handa
2010-02-17 6:11 ` Stefan Monnier
2010-02-17 6:26 ` Kenichi Handa [this message]
2010-02-17 7:31 ` Alfred M. Szmidt
2010-02-17 19:34 ` Stefan Monnier
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=tl7mxz8qsxi.fsf@m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=expire-by-2010-02-18@kanis.fr \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.