|
|
|||||||||||||||||||||||||||||
![]() |
![]() |
||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||||||||||||||
|
13.2 Updating with the import command
When a new release of the source arrives, you import it into the
repository with the same
For files that have not been modified locally, the newly created
revision becomes the head revision. If you have made local
changes,
The above command will check out the latest revision of `wdiff', merging the changes made on the vendor branch `FSF_DIST' since yesterday into the working copy. If any conflicts arise during the merge they should be resolved in the normal way (see section 10.3 Conflicts example). Then, the modified files may be committed. Using a date, as suggested above, assumes that you do not import more than one release of a product per day. If you do, you can always use something like this instead:
In this case, the two above commands are equivalent.
|
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
|
Marketplace: | |||||||||||||||||||||||||||||
| " According to a June 2004 study by Sandvine, 80% of all spam is sent by infected Windows PCs. " | |||||||||||||||||||||||||||||