From: Neil Jerram <neil@ossau.uklinux.net>
To: guile-devel@gnu.org
Subject: Re: another merge from 1.8
Date: Sun, 28 Jan 2007 17:14:18 +0000 [thread overview]
Message-ID: <87tzybxedx.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87odovappg.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 19 Jan 2007 10:18:51 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
[about an IA64 HP-UX fix...]
>> Have you already done the merge of these changes to 1.8,
>
> No.
>
>> or should I do that?
>
> Yes please.
I've done this now.
One detail of the merging... I gather we're preferring to merge
ChangeLog fragments directly, so as to minimize the diffs between the
ChangeLogs in two branches, rather than say inserting the relevant
entry at the top of the ChangeLog in the target branch.
This seems fine to me, but it does mean we lose info about when the
change was actually added to the target branch. So to remedy that
I've added a note, making an entry read like this:
2006-10-25 Neil Jerram <neil@ossau.uklinux.net>
(Merged from CVS HEAD on 2007-01-28.)
IA64 HP-UX patch from Hrvoje Nikšić. (Thanks!)
* configure.in: New check for uca lib (needed for IA64 on HP-UX).
Then only the added note line shows up as a diff.
If that sounds good, it would make sense for us all to do this when
merging.
I also had to specify a new encoding for the 1.8 ChangeLogs, and
guessed utf-8. I'm afraid I don't really understand this area, so
please shout if that was wrong.
>>> * Is the readline "new-input-prompt" bit meant to be in 1.8?
>>
>> That one's debatable. It seems on reflection that the change wasn't
>> directly related to the reported (by Jon Wilson) problem. So it
>> should probably be considered an enhancement, not a bugfix - hence not
>> for 1.8.
>
> I think modest enhancements are definite 1.8 material, no need to wait
> the 3 years for a head release, not for bits that are safe and self
> contained.
I agree - if we can't manage less than 3 years. I'd prefer to have
more frequent releases and better release machinery though. I'm going
to try working on that for a while.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-28 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 0:05 another merge from 1.8 Kevin Ryde
2007-01-16 12:13 ` Ludovic Courtès
2007-01-17 23:03 ` Neil Jerram
2007-01-18 23:18 ` Kevin Ryde
2007-01-28 17:14 ` Neil Jerram [this message]
2007-01-30 0:34 ` Kevin Ryde
2007-02-06 22:57 ` Neil Jerram
2007-02-07 23:12 ` Kevin Ryde
2007-02-18 23:36 ` Neil Jerram
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tzybxedx.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-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.
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).