Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>May be just have a git repo with the minimum number of file in it:</p> <p>one: <code>.gitignore</code> with obvious ignore patterns in it.</p> <p>And then clone that "almost empty" repository.<br> Note that such an "almost empty" repository ("almost" because it still has a minimal working directory alongside the .git directory) can then by '<code>git clone --bare</code>' (as <a href="https://stackoverflow.com/questions/738154/what-does-git-updating-currently-checked-out-branch-warning-mean">illustrated here</a>), making it a true bare repo (but not an "empty" one).<br> This is that bare repo you can then:</p> <ul> <li>clone everywhere you want.</li> <li>or (more importantly) push to (since it is a bare repo)</li> </ul> <hr> <p>You have in <a href="http://kerneltrap.org/mailarchive/git/2007/7/13/251504/thread" rel="nofollow noreferrer">this thread</a> a good summary of the "other way around" (which I keep here for reference).</p> <pre><code>$ git-init $ git-remote add origin server:/pub/git/test.git </code></pre> <blockquote> <p>For a new project (no code yet) I wanted to make an empty, bare<br> repository (no working copy) on a remote public server as a starting<br> point, clone it locally, and gradually create content locally and<br> push it out to the remote, public server.</p> </blockquote> <p>To which Junio C Hamano responded:</p> <blockquote> <p>You prepared an empty bare repository for publishing, and that is very good.</p> <p>The next step is that you prepare your contents elsewhere. That would be your private working place, i.e. the place you would normally work in).<br> You push from your private working place into that publishing repository.<br> Your working place is where the very initial commit should come from, since you are the one who is starting the project.</p> <p><strong>Note that the private working place does not have to be a clone of the empty one. That actually is backwards. Your work started from your private working place to the publishing one.</strong></p> <p>You could even clone your private repository to publishing one to make it clear who is the master and who is the copy if you wanted to, but because you already have the bare repository for publishing, just pushing into it is all that is needed.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the most straightforward way to clone an empty, *bare* git repository?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat's the most straightforward way to clone an empty, *bare* git repository?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm creating a *bare* git repo so there is *no* working directory. Perhaps I need a standard 'almost empty' repo in a standard place which I can then push to an empty repo?
      singulars
      1. PO
      1. USNorman Ramsey
    2. COBut once you create an "almost empty" repos, you can 'git clone --bare' it and make it a true bare repo ( http://stackoverflow.com/questions/738154/what-does-git-updating-currently-checked-out-branch-warning-mean )
      singulars
      1. PO
      1. USVonC
    3. COIf create an almost empty repo, I may as well just push from it to a newly initialized bare repo. If you don't mind scraping the extra cruft off your answer, I could upvote it :-)
      singulars
      1. PO
      1. USNorman Ramsey
 

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