-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 22 Sep 2004 17:33, Mathieu Roy wrote:
> Elfyn McBratney <[EMAIL PROTECTED]> tapota :
> > Hi,
> >
> > I'm just benching my index additions/modifications and then I'll commit
> > them. One thing before, I do: do I lump them in with the .structure files
> > (easier and less error prone for those that use mysqldump) or give them a
> > new .index (or similar) file suffix (easier for me to hack on now ;-) ?
> >
> > I think Mathieu uses mysqldump. (no?)
>
> I used to but I havent done it since a long time. It's up to you.

Ok.

> > If it would make things easier, I'll stick with that add add 'em to
> > the .structure files.
> >
> > Also, there are a lot of comments in the sql and php (I've added marker
> > comments to db_query & co. so I and others can easily find where they are
> > and if they've changed).  Is that ok? :-)
> >
> > If any of this causes merge conflicts, please ping me, and I'll work with
> > anyone making changes to get HEAD fixed.
>
> Hum, Elfyn, I'd prefer you make this commit after release 1.0.4. I'm
> afraid of introducing now new stuff for this release. Two days before
> the release, only bugfixes and cosmetics should be done.
>
> Is it okey for you?

Totally cool. :-)  Hmm, it will be easier all round if I do this on a branch 
(and MFH as and when).  When your ready, we could merge it to HEAD, table by 
table - or all at once, and I'll fix any conflicts.

I might wait and branch once you release, then it'll be easier to MFB back to 
HEAD.

Sound good? :-)

> We can make a new release in 2 weeks just for this database stuff, I
> have no problem with this idea.

Excellent. :-)

Thanks,
Elfyn

- -- 
Elfyn McBratney
beu on irc.freenode.net/savannah.[non]gnu.org

PGP Key ID: 0x456548B4
PGP Key Fingerprint:
  29D5 91BB 8748 7CC9 650F 31FE 6888 0C2A 4565 48B4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBUa6HaIgMKkVlSLQRAjYBAJ9Z3aRq1tC64flzoGUtUxTmOzEtzQCgoVQy
WOEqa/J6HbRwIKG2CLuyh7A=
=divS
-----END PGP SIGNATURE-----

Reply via email to