From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: small mistakes in unicode branch update
Date: Tue, 20 Apr 2004 10:28:29 +0900 (JST) [thread overview]
Message-ID: <200404200128.KAA01933@etlken.m17n.org> (raw)
In-Reply-To: <20040419130434.GA10902@fencepost> (message from Miles Bader on Mon, 19 Apr 2004 09:04:34 -0400)
In article <20040419130434.GA10902@fencepost>, Miles Bader <miles@gnu.org> writes:
> If you want to try to use arch for working on unicode emacs, you can either
> use that branch, or make your own branches tagged off of it (note that
> `tagging' in arch is fairly different than tagging in CVS), and occasionally
> merge changes back the other direction. Either way, commits to it will be
> propagated back to CVS.
> Another possible use is to keep the unicode branch up-to-date with respect to
> the trunk by regularly merging from emacs--cvs-trunk--0 to emacs--unicode--0
> (I do this about once week with my private branches). Since the basic
> mechanics of merging in arch are far less painful than in CVS, it's often a
> good idea to merge often so that conflicts don't accumulate.
Thank you for the info. I'll do the latter.
---
Ken'ichi HANDA
handa@m17n.org
prev parent reply other threads:[~2004-04-20 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <buollksfzk7.fsf@mcspd15.ucom.lsi.nec.co.jp>
[not found] ` <200404190537.OAA29065@etlken.m17n.org>
2004-04-19 7:47 ` small mistakes in unicode branch update Miles Bader
2004-04-19 11:33 ` Kenichi Handa
2004-04-19 13:04 ` Miles Bader
2004-04-20 1:28 ` Kenichi Handa [this message]
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=200404200128.KAA01933@etlken.m17n.org \
--to=handa@m17n.org \
--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).