Re: Merged branch with history

[Dustin J. Mitchell]

On Sun, Aug 2, 2009 at 10:48 AM, Francesco
Salvestrini<address@hidden> wrote:
> A straight master/maint merge and a mass-move of all macros into the m4
> directory seems the less troublesome way, at a first glance.
>
> Since we're going to generate a per-macro-history-page automatically ... which
> is the best rearrangement which eases the automatic-history generation too ?

Not to be too forceful here, but with the number of projects going on
here, I'd like to just get this one done.  Let's use the octopus merge
to pretend that the macros have *always* been in the m4/ subdirectory.
 This moment will fade into history and we will soon have forgotten it
completely.  The current gitweb-based history mechanisms will still
work until we develop something new.  There's really no downside here!

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com