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

List:       kde-i18n-doc
Subject:    Re: KDE tarballs released to the packagers
From:       Eric Bischoff <ebisch () cybercable ! tm ! fr>
Date:       2000-10-17 11:31:38
[Download RAW message or body]

Stephan Kulow wrote:
> 
> You only commit to one branch, if you want to commit to both, you
> will have to do extra work.
> You decide once on cvs update to use the 2_0 in using
> cvs update -r KDE_2_0_BRANCH. Unless you use cvs update -A, the update
> will stick to this branch and commit will commit to this branch.
> You should that's why commit without -m to see in which branch you're
> commiting (if you don't know vi - use export EDITOR=emacs ;-)
> 
> So if you want to commit regulary to both branches, you better keep
> two copies.

Thanks for those explanations.

Hmmm... This is somehow of a problem because most people will want to
commit to both branches most of the time, at least during a certain
time. So I think it's a good idea to use systematically update -A.


-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

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