Nathan,
rc = resource file as used in C++ applications
co = checkout
ci = commit (svn abbreviation)
wc = working copy
Tom
-----Original Message-----
From: Nathan Nobbe [mailto:quickshiftin@gmail.com]
Sent: Monday, June 18, 2007 8:21 PM
To: Tom Kielty
Cc: users@subversion.tigris.org
Subject: Re: Doing builds with subversion
perhaps im a bit of a newb; can you spell out some of the terms youve
abbreviated for me?
On 6/18/07, Tom Kielty <tom.kielty@calabrio.com> wrote:
> Thanks for the information. I have been working on our process since
> this e-mail. Currently I am doing a tag then a co from the tag. Also
for
co = checkout
> the rc's I am logging each rc that is updated and then doing a single
ci
rc = ?
ci = check in?
> at the end of the build process into the tag. That is working great.
>
> However, the issue I am dealing with now is how to accomplish merge
> discussed below. As my WC is from the tag when a developer has a
build
WC = working copy
> fix I thought he could tell me the revision number of his ci. Then I
> would merge that revision with the tag and be good to go. What I did
not
> understand was that the merge, merges with my WC not the tag. So then
I
> need to ci the tag. But at that point I have many other files that are
> either updated (the rc's) or new and the ci gets flagged. So it seems
> that I need to do an explicit ci for the updated files. What I am
> worried about is how much manual work this is and if there are many
> files that are updated it will take a lot of time to get these updated
> in the tag.
>
> Is there a simpler approach to do a merge and only ci those files to
the
> tag when other files are flagged as modified or un-versioned?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 19 05:13:31 2007