From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: Miles Bader <miles@gnu.org>, Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus 5.11 in Emacs CVS
Date: Wed, 14 Apr 2004 22:24:23 +0200 [thread overview]
Message-ID: <v9oepugvew.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87znbl2oqd.fsf@tc-1-100.kawasaki.gol.ne.jp>
On Sun, Feb 15 2004, Miles Bader wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>> If we need a branch, shouldn't it be in _Emacs_ CVS to test the
>> integration (e.g. check that new files have to be added to CVS, ...)?
>> I wonder how the merge has been done last time. I'd like to help with
>> it, but probably it would make more sense if someone with write access
>> to Emacs CVS does the first (big) step.
>
> Instead of CVS, you could use tla (aka `arch') and my emacs arch branch,
> which is synchronized with the emacs CVS trunk.
>
> tla allows (painlessly) distributed repositories, and generally uses a
> `pull' model, so write access to a central repository isn't necessary.
> It is also much better at merging than CVS.
Do I understand you correctly that if I managed to merge Gnus into an
arch archive of Emacs, you would sync the archive to Emacs CVS trunk?
I've never used tla before. I installed it now and will read some
introductory documentation soon (from wiki.gnuarch.org). It would be
very helpful for me if you could give me a brief (or even better: not
so brief ;-)) description of the necessary steps.
> One part of this is that I've added `taglines' to all the emacs source
> files (in CVS), which make it easy to assign a unique identity to each
> file (even if the name changes).
>
> If you'd accept a patch against Gnus CVS to add taglines, this would
> make future merging using tla easier.
I cannot speak for Lars, but I don't think he would refuse. Lars?
(If Lars agrees on this, I can commit your patches to Gnus CVS).
> This is slightly trickier than with a new project, because Gnus and
> Emacs conceptually _share_ files (even though the actual contents may
> vary), so it would be best to use the _same_ tagline for the same file
> in both Gnus and Emacs.
Apart from the trunk, we have a branch "v5-10" for the 5.10 series.
Probably they should be added in both branches?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-04-14 20:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 11:01 Per Abrahamsen
2004-01-05 21:18 ` Steve Youngs
2004-01-05 22:01 ` Reiner Steib
2004-01-06 5:08 ` Lars Magne Ingebrigtsen
2004-01-08 17:58 ` Reiner Steib
2004-01-13 22:22 ` Reiner Steib
2004-01-13 23:08 ` Jesper Harder
2004-01-14 5:15 ` Jesper Harder
2004-01-14 6:20 ` Simon Josefsson
2004-01-15 0:46 ` Jesper Harder
2004-01-15 2:30 ` Simon Josefsson
2004-01-14 14:18 ` Reiner Steib
2004-01-22 7:43 ` Jesper Harder
2004-01-22 15:17 ` Reiner Steib
2004-02-15 0:03 ` Miles Bader
2004-02-15 0:18 ` Miles Bader
2004-04-14 20:24 ` Reiner Steib [this message]
2004-04-15 0:37 ` Miles Bader
2004-05-12 10:17 ` Reiner Steib
2004-01-05 22:12 ` Xavier Maillard
2004-01-06 13:46 ` Per Abrahamsen
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=v9oepugvew.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=larsi@gnus.org \
--cc=miles@gnu.org \
--cc=reiner.steib@gmx.de \
/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).