From: "Roland Caßebohm" <roland.cassebohm@visionsystems.de>
To: "Reinhard JESSICH" <Reinhard.JESSICH@frequentis.com>,
<gary@mlbassoc.com>, <grante@visi.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Keeping 2.0 source tree up to date
Date: Mon, 29 Sep 2003 15:50:00 -0000 [thread overview]
Message-ID: <200309291750.28277.roland.cassebohm@visionsystems.de> (raw)
In-Reply-To: <sf704491.019@mail.frequentis.com>
On Dienstag, 23. September 2003 13:03, Reinhard JESSICH wrote:
> I would *not suggest* using the vendor branch feature of CVS directly on
> the main branch, as you might end up with an inconsistent state (at least
> temporarily).
>
> Here is what we are doing:
>
> We checked out a local copy from the annon CVS. Then we imported
> it to our CVS main branch with the "cvs import" command. After that we
> created a branch and started our own developments on this branch.
>
> We have a cron job running, which will update the local copy of the annon
> CVS weekly and generate a diff report about the ChangeLog files. This
> report is checked by the developers and if there is an interesting change,
> we import from the local copy of the annon CVS to our main branch "cvs
> import vendor-tag release-tag". We do this at least once in two months, to
> keep track of the ongoing development.
Is vendor-tag everytime the same, or do I have to rename it everytime I call
cvs import?
With release-tag I will do somthing like release-yyyy_mm_dd, but I'm not
sure what to do with the vendor-tag.
Thank you,
Roland
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-09-29 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 11:03 Reinhard JESSICH
2003-09-29 15:50 ` Roland Caßebohm [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 3:16 Reinhard JESSICH
[not found] <sf787ac4.077@mail.frequentis.com>
2003-09-29 16:37 ` Roland Caßebohm
2003-09-23 11:32 David Vrabel
2003-09-22 14:44 Grant Edwards
2003-09-22 15:17 ` Andrew Lunn
2003-09-22 18:59 ` Grant Edwards
2003-09-22 19:11 ` Gary Thomas
2003-09-22 19:20 ` Grant Edwards
2003-09-22 19:29 ` Gary Thomas
2003-09-22 19:34 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309291750.28277.roland.cassebohm@visionsystems.de \
--to=roland.cassebohm@visionsystems.de \
--cc=Reinhard.JESSICH@frequentis.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.com \
--cc=grante@visi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).