Re: What's cooking in git.git (topics)
- From
Andreas Ericsson <ae@op5.se>
- Date
- Nov 27, 2007, 15:18 UTC
- Message-ID
- <474C352A.2080708@op5.se>
- In-Reply-To
- <Pine.LNX.4.64.0711271352050.27959@racer.site>
Johannes Schindelin wrote:
Show 14 quoted lines
> Hi, > > On Tue, 27 Nov 2007, Andreas Ericsson wrote: > >> Johannes Schindelin wrote: >> >>> One thing that could go possibly wrong, for example, is to rebase >>> commits that you already published. >> For the vast majority of git users, that's a non-issue as "published" is >> usually defined as "pushed to the publicly advertised watering hole". > > No. This is only the "vast majority of git users told by their peers to > use a central repository". >
Let me rephrase. For any project large enough to want to attract random hackers, there will always be a single repository considered the public "master repo". For such projects code is most likely considered "published" when the code hits that repository (or some middle-stage on its way to it).
It has to do with communication and convenience. When the code reaches that master repo it's no longer easy to communicate the fact that it has been rebased to everyone it's been published to.
> Just because you use git like cvs does not mean that you "use git". >
I suppose Junio and Linus don't "use git" either then, as they're both in control of at least one such "master repo" each. Ah well. At least I'm in good company.
Show 5 quoted lines
>> Yes, I'm aware that git is distributed. That doesn't mean that it's not >> convenient to have one single place where all code meant to be released >> eventually ends up. > > It may be convenient for you. I do not like it.
It's not only convenient for me. It's convenient for the tens of thousands of people working on the Linux kernel to have a single place to go to for that one repository that somehow fathers all the tarballs.
So long as it's a small group of developers working on something, it's obviously not necessary to provide such a place, but when you want to attract the huge anonymous coders that you've never spoken to, you need a single place to post the latest and greatest.
Show 5 quoted lines
> Yes, I even made the > mistake with msysGit. In the end, it would have been much more > intelligent to set up a repository which others would have had to fork > from. >
So? Any new developer wanting to work on it will still try to locate the public copy of the "master repo" to start their fork from.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231