bug-hurd
[Top][All Lists]
Advanced

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

Re: News...


From: Thomas Schwinge
Subject: Re: News...
Date: Tue, 7 Jul 2009 19:10:15 +0200
User-agent: Mutt/1.5.11

Hello!

On Sun, Jul 05, 2009 at 07:21:08PM +0200, Arne Babenhauserheide wrote:
> Am Samstag, 4. Juli 2009 17:13:17 schrieb Thomas Schwinge:
> > Just a quick comment: instead of altering the existing announcement now,
> > what about publishing these (undoubted!) enhancements in the next one --
> > by then these changes will (I expect) be present in the master sources.
> 
> That's a nice idea. 
> 
> Can you put my changes into a branch to be merged next month? 

That's actually a nice scheme: we'll have a branch master-news_next where
we work on the current month's news item (that is, add new stuff to it as
soon as it arises), and then, when we have settled on what we intend to
publish, we'll merge that branch into master and have the news item
published that way.

We should not update news items that have already been published (that
is, on gnu.org; no problem for the bddebian machine), as the system will
always also update the RSS feeds, etc., causing the old news item to
reappear on feeds, which is a bit of a nuisance.

After having merged master-news_next into master, work for the next
month's news item can continue on master-news_next.

> (I'd like to have them in the main repo, but the last time I haggled with git 
> branching I had to reclone my local repo)

You already did put your changes (creating the July news item) into the
master branch, so what I had to do now was reverting that commit on the
master branch, but preserve the changes you had done on the new
master-news_next branch.  This is now in a state that it's usable.  On
flubber, that is.  If someone also wants to see it on the Savannah
hurd/web Git repository, just talk to me.

The instructions from
<http://lists.gnu.org/archive/html/bug-hurd/2008-11/msg00129.html>
basically still apply, replacing homepage with master-news_next, of
course.  If there are concrete questions about how to handle these two
branches (master and master-news_next), then please ask -- before pushing
experiments to flubber.


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature


reply via email to

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