Re: arch patch queue manager
Martin Bayer <[email protected]>
| Newsgroups | gmane.comp.video.gephex.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |>"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? | | Why the -S flag? I think I created the branch by first doing "tla | setup-archive gephex--georg--0.4" | followed by a "tla tag" (without flags). | (Cannot verify this at the moment, maybe the syntax is wrong) The "-S" flag just creates the archive if it doesn't exist yet. I tried it without -S but that doesn't change the behaviour. What version of tla are you using? I use "tla-1:20040206-1.lord" perhaps my release doesn't like the cacherev cause it has no valid checksum attached. - -- 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 iD8DBQFAJRYDCm3i57PRsbsRAtdCAKDDXKF0spXVJXEmUBcen8Ky6LGRbACfQQ0L bGSVG94MrwBs9NhuQoV8OJA= =3oVI -----END PGP SIGNATURE-----