Re: Cloning empty repositories, was Re: What is the idea for bare repositories?
- From
Bill Lear <rael@zopyra.com>
- Date
- Nov 12, 2007, 17:55 UTC
- Message-ID
- <18232.37763.897729.895378@lisa.zopyra.com>
- In-Reply-To
- <Pine.LNX.4.64.0711121727130.4362@racer.site>
On Monday, November 12, 2007 at 17:30:10 (+0000) Johannes Schindelin writes:
Show 19 quoted lines
>Hi, > >On Mon, 12 Nov 2007, Bill Lear wrote: > >> We have an administrator create a new bare repo for us, and we populate >> it by pushing into it. It wold be nice if the administrator could >> create a bare repo and we could clone from it, and push to it to >> populate it, instead of cloning the bare repo from another repo that has >> already been (partly) populated. > >I don't see what is soooo hard with using git-remote in the repo you are >pushing from. It's just a "git remote add origin <url>", and you can even >use this to push right afterwards: "git push --all origin". > >Besides, if you really want to work together, chances are that you do >_not_ want to start with <n> independent initial commits. So you need to >populate the repository before starting _anyway_. > >Why are easy solutions so unattractive?
Well, 1) to answer your first point: it's not soooo hard, but it's an extra step that just seems unnecessary. 2) It's not the *easiest* solution that one can think of, so people naturally complain: "why do I have to push in the clutch AND select the gear"?
Bill