[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: another gnulib update

From: Gary V. Vaughan
Subject: Re: another gnulib update
Date: Sun, 25 Feb 2007 19:20:05 -0800

Hi Bruno,

On 25 Feb 2007, at 18:25, Bruno Haible wrote:
Eric Blake wrote:
Eventually, when the move to git is complete, doing this will be easy - you just make a branch in your local git copy of gnulib, and base your m4
release off of that branch.

git will certainly help in doing so.

But what Gary also wants is the knowledge, that we 4 (you, Paul, Jim, me) have: what is a good starting point and what additional patches are recommended
on top of that.

Yes indeed, but I don't only want it for me.  I'm hoping we can come
up with a (semi-)automated way of providing that information to all
current and future gnulib client projects.

For today, I would say, take as starting point the day before the <time.h> and <string.h> changes, a month ago. Then each of us can give Gary a list of
recommended ChangeLog entries that he can integrate in his "branch".

Is there any reason why every now again a particular revision of the
gnulib tree can't be blessed as the stable branch point, and change sets
that are purely bugfixes marked as such?  That would mean anyone that
wants to build a local stable branch for the release of their own
gnulib-using-project can take the most recently blessed revision and
cherry pick the relevant bugfix changesets.

Is there perhaps some way to cleverly tag the CVS tree of gnulib to
avoid this problem?

Hardly. Often it's clear only after two or three weeks whether a patch
was good or not. We don't know at the moment the patch is committed.

True enough.

I think that my argument depends on whether we can reach a consensus
that gnulib has reached a tipping point where the extra work for the
gnulib contributors (blessing releases and marking bugfix changesets
as such) saves a greater amount of work by gnulib users (trying to
work out how to build a good stable gnulib snapshot to release their
project against).

  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_ Join my AGLOCO Network: http://www.agloco.com/r/BBBS7912

Attachment: PGP.sig
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]