[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kc-kde
Subject:    Re: [kc-kde] CVS?
From:       Juergen Appel <predator1710 () gmx ! de>
Date:       2002-05-09 20:59:01
[Download RAW message or body]

Am Mittwoch, 8. Mai 2002 16:49 schrieb Aaron J. Seigo:
> On May 7, 2002 05:05 pm, Timothy R. Butler wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> >   Just wondering what's up with KC-KDE and cvs?
>
> i'm finally back and able to start spending time on KDE stuff again. so i'd
> like to start the process of getting a KC KDE out for next week. i'll
> provide summaries for devel and core-devel and help the new editors out on
> their first issue.
>
> as for cvs, cvs co kckde ... you'll find the first 36 issues in there which
> i just committed... now we can start adding to it =)
>
> > Are all the editors going
> > to be given CVS access to the kc-kde module, or will I submit my
> > summaries to someone (who?)?
>
> i think it would be best if all the editors had CVS access. it will make it
> that much easier.

agreed, ill ask david for id & pass.

> however, since they are all single files we should be
> careful to make sure that we aren't all editting the same issue all at once
> and end up having huge conflicts to merge.
>
> i'd suggest that we do it the same way we did it in the past: post your
> summaries here to the list for proofing and the editor can merge it into
> the new issue.

so whats the use then of cvs?

>
> if you see errors in the new issue, post the "patch" here as well and let
> the editor merge it.
>
> of course, another option would be to create a directory for each issue and
> keep each summary in its own file in that directory for easier CVS'ing and
> then the editor could compile all those bits into the final issue. i don't
> think that would really be worth it though ... but perhaps i'm wrong =)


_______________________________________________
kc-kde mailing list
kc-kde@mail.kde.org
http://mail.kde.org/mailman/listinfo/kc-kde
[prev in list] [next in list] [prev in thread] [next in thread]