From: Karl Fogel <kfogel@red-bean.com>
To: David Kastrup <dak@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Release procedure.
Date: Mon, 07 May 2007 09:14:22 -0700 [thread overview]
Message-ID: <87mz0gvcf5.fsf@red-bean.com> (raw)
In-Reply-To: <861wht17al.fsf@lola.quinscape.zz> (David Kastrup's message of "Mon\, 07 May 2007 08\:23\:14 +0200")
David Kastrup <dak@gnu.org> writes:
> Well, but we _did_ branch, and there is a complete lack of directions
> about what the branch is supposed to be for. Previously it was agreed
> that we'd use the trunk after branching for merging in multi-tty and
> emacs-unicode-2, and use the branch for the 22.x series.
>
> At the current point of time, however, it appears like both trunk and
> release branch are not supposed to be worked upon except by special
> notice, and then both are synchronously updated.
>
> It does not make sense, and it makes it impossible for anybody to do
> serious work.
I can't confidently assert that there's a complete lack of direction
about what the branch is for, because it's always possible that there
was such direction and I simply didn't see it (although a permanent
file in the tree would be better than a mailing list post, for that).
But, just as a data point: I'm in the same boat with David. For
whatever reason, I also do not understand what the branch is for.
next prev parent reply other threads:[~2007-05-07 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 1:34 Release procedure Karl Fogel
2007-05-07 2:25 ` Stefan Monnier
2007-05-07 3:18 ` Karl Fogel
2007-05-07 6:23 ` David Kastrup
2007-05-07 16:14 ` Karl Fogel [this message]
2007-05-07 16:38 ` Chong Yidong
2007-05-07 21:01 ` 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
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=87mz0gvcf5.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).