Re: arch patch queue manager

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

Hi,

| Another thing: I changed the owner and permissons of /var/arch/gephex,
| now only user gephex can commit there. So you are "forced" now to use
| the pqm if you want to commit ;)

I'll do my best to follow your evil plan :)

I have a question about branching with tla. I need to branch from
gephex--main--0.4 for the v4l refactoring stuff. If i do this with

"tla tag -S [email protected]/gephex--main--0.4
[email protected]/gephex--refactor-v4l--0.4"

tla fetches the base-0 revision and the 1726 patches from the
[email protected] archive. Creating a microbranch is a quite time
intensive operation if tla does it this way. Why doesn't tla use the
cacherev at patch-1722 and patches it up to the newest revision?

| The remaining TODOs are:
|
|     - cron job that calls arch-pqm --run
|     - create one branch of gephex--main--0.4 and gephex--main--0.5 for
|       every developer and tell arch-pqm where it is
|       (those branches can be on different archives, so for example martin
|        could have his archive on tyr, I could mirror my offline archive
|        to gephex.org, ...)

My tla archive is at http://arch.gephex.org/martin and my current
development branch is gephex--refactor-v4l1--0.4. I'm not sure if it
would be better to create an extra "ready-to-merge" branch.  How do you
plan to organize your microbranches?

|     - add other public keys to gephex keyring

I added my key.

Martin

- --
GnuPG (ID B3D1B1BB) C2F4 F775 5022 1891 48F4  761D 0A6D E2E7 B3D1 B1BB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAJQGRCm3i57PRsbsRAqmlAJ9LfQRU8yV5VXW3QRFVRux0KHltswCgu7mX
ztsoLeQ0lp58PKEk8Fpidfg=
=oePi
-----END PGP SIGNATURE-----