unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: small mistakes in unicode branch update
Date: Mon, 19 Apr 2004 09:04:34 -0400	[thread overview]
Message-ID: <20040419130434.GA10902@fencepost> (raw)
In-Reply-To: <200404191133.UAA29998@etlken.m17n.org>

On Mon, Apr 19, 2004 at 08:33:20PM +0900, Kenichi Handa wrote:
> >    miles@gnu.org--gnu-2004/emacs--unicode--0
> 
> > It will be kept updated from the emacs-unicode-2 CVS branch.
> 
> It seems that it is the branch Stephen mentioned in "Well,
> you'll have to create an Arch branch first.", right?

Yes, I guess so.

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.

-Miles
-- 
Somebody has to do something, and it's just incredibly pathetic that it
has to be us.  -- Jerry Garcia

  reply	other threads:[~2004-04-19 13:04 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 [this message]
2004-04-20  1:28         ` Kenichi Handa

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=20040419130434.GA10902@fencepost \
    --to=miles@gnu.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).