-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen van der Drift wrote:
| Thanks. Unfortunately I don't have the time to maintain and test my
| packages in two trees. Do you guys recommend to keep using the
| pangocairo tree, or the original one? In the latter case, how do I go
| back?
If you do
>Koen van der Drift wrote:
>|
>| On Apr 27, 2008, at 8:54 PM, Benjamin Reed wrote:
>|
>|> You are welcome to update it in both, but if you don't, we'll
>|> periodically merge cahnges from trunk into pangocairo to make sure it's
>|> ready for when it's time to merge back.
>|
>| How do I update a pa
On 28 Apr 2008, at 01:13, Martin Costabel wrote:
> Kevin Horton wrote:
> []
>> pangocairo tree, as described on the wiki. Can I update the CVS
>> settings for that tree to switch it from anonymous CVS to my
>> sourceforge ID so I can commit changes, or do I need to do a new
>> checkout f
Kevin Horton wrote:
[]
> pangocairo tree, as described on the wiki. Can I update the CVS
> settings for that tree to switch it from anonymous CVS to my
> sourceforge ID so I can commit changes, or do I need to do a new
> checkout first?
I'd run a little shell script along the lines of
fo
On 27 Apr 2008, at 20:54, Benjamin Reed wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kevin Horton wrote:
> | Now that the pangocairo branch is starting to emerge, what should
> non-
> | core maintainers do when they update a package in the main
> branch? I
> | assume that we s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen van der Drift wrote:
|
| On Apr 27, 2008, at 8:54 PM, Benjamin Reed wrote:
|
|> You are welcome to update it in both, but if you don't, we'll
|> periodically merge cahnges from trunk into pangocairo to make sure it's
|> ready for when it's time to
On Apr 27, 2008, at 8:54 PM, Benjamin Reed wrote:
> You are welcome to update it in both, but if you don't, we'll
> periodically merge cahnges from trunk into pangocairo to make sure
> it's
> ready for when it's time to merge back.
How do I update a package in both trees, is this documented so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Horton wrote:
| Now that the pangocairo branch is starting to emerge, what should non-
| core maintainers do when they update a package in the main branch? I
| assume that we should also update it in the pangocairo branch
| (assuming it builds a
Now that the pangocairo branch is starting to emerge, what should non-
core maintainers do when they update a package in the main branch? I
assume that we should also update it in the pangocairo branch
(assuming it builds and works OK there). Or, should we just update
it in the main branch
