Larry,
Thank you for making importing clear.
Jeanie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 09, 2002 12:28 PM
To: Schwenk, Jeanie
Cc: [EMAIL PROTECTED]
Subject: Re: question about importing
Schwenk, Jeanie writes:
>
> T
On Mon, Sep 09, 2002 at 11:54:14AM -0700, Stan Berka wrote:
> At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote:
> >[...] I rarely use the modules file anyway.
>
> If you don't use modules file, how do you get the list of modules in the
> repo w/o going to the repo manually and browsing what fold
Schwenk, Jeanie writes:
>
> This is regarding a vendor branch. When the vendor sends us a new version,
> we import rather than add. This is per Cederqvist 13.2 "Updating with the
> import command" and Chapter 6 "Tracking Third-Party Sources: Vendor
> Branches" in Fogel's book. Perhaps I have
On Mon, 9 Sep 2002, Stan Berka wrote:
> At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote:
> >"import" could arguably pay attention to the modules file -- but
> >I'm not going to be the one to argue for it :-) since (a) I don't
> >know what "pay attention to" would mean in practice, and (b) I
> >ra
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 09, 2002 12:03 PM
To: Schwenk, Jeanie
Cc: [EMAIL PROTECTED]
Subject: Re: question about importing
Schwenk, Jeanie writes:
>
> After the original import, why do you have to give the full path in the
> repository to where
Schwenk, Jeanie writes:
>
> After the original import, why do you have to give the full path in the
> repository to where the imported files are to do? Is it because an import
> assumes nothing even when there are CVS directories?
When there are CVS directories where? In the directory you're
i
Eric,
At 02:39 PM 9/9/2002 -0400, Eric Siegerman wrote:
>"import" could arguably pay attention to the modules file -- but
>I'm not going to be the one to argue for it :-) since (a) I don't
>know what "pay attention to" would mean in practice, and (b) I
>rarely use the modules file anyway.
If you
On Mon, Sep 09, 2002 at 11:17:12AM -0700, Schwenk, Jeanie wrote:
> After the original import, why do you have to give the full path in the
> repository to where the imported files are to do? Is it because an import
> assumes nothing even when there are CVS directories?
Correct. An import of a t
After the original import, why do you have to give the full path in the
repository to where the imported files are to do? Is it because an import
assumes nothing even when there are CVS directories?
I ask because I just did the second import of vendor code and the result was
not what I expected.
