Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To explain a little more clearly, the -no-trees option means that a working tree is not kept for any of the branches stored within the repository.</p> <p>What does that mean?</p> <p>1) The repository doesn't hold your source files. Don't believe me? Go cd into a branch inside a no-trees repository and tell me what a "ls" gets you. Nothing.</p> <p>Now, what is actually stored there is the HISTORY of the files, so that a file can be reconstructed from that history.</p> <p>2) You can't work inside a no-trees repository as there is no working tree. You discovered this yourself - you can't commit. Why not? Because the files aren't there. Only their history is.</p> <p>So, what good are no-trees repositories? Like was stated, they're good for a central server. If you and Bob are working on a project, and you're not always going to be able to push/pull from each other's personal machines, or you work in a company that wants a place for the latest clean "trunk" then a shared server with a no-trees repository is your answer.</p> <p>Here's how it works. You create the repository on the shared server with the no-trees option and then import your "trunk" into the repository.</p> <p>You then pull down the latest copy of the "trunk" with something like bzr branch bzr+ssh://mysharedserver/myrepo/trunk trunk_mirror</p> <p>That gets you a "mirror" copy of the trunk. You then create branches off of that mirror copy for your new features, bugfixes, etc, committing all you want. </p> <p>Now you're going out of town and Bob needs your code. Since it's ready, you merge it into the trunk mirror:</p> <p>cd trunk_mirror bzr merge ../my_really_cool_feature_branch bzr commit "added my cool feature to trunk" bzr push</p> <p>The last step pushes your changes to the mirrored trunk up to the shared repository where Bob will be able to do a "pull" and get the latest copy of the trunk.</p>
    singulars
    1. This table or related slice is empty.
    1. POTrying to understand BZR repository II
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USwadesworld
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTrying to understand BZR repository II
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis answer really clear thing up. Thanks alot.
      singulars
      1. PO
      1. USNawaMan
    2. COsounds like `--bare` in `git init`
      singulars
      1. PO
      1. UShasen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload