Re: What's cooking in git.git (topics)
- From
Andreas Ericsson <ae@op5.se>
- Date
- Nov 27, 2007, 13:45 UTC
- Message-ID
- <474C1F80.5060404@op5.se>
- In-Reply-To
- <Pine.LNX.4.64.0711271109130.27959@racer.site>
Johannes Schindelin wrote:
Show 15 quoted lines
> Hi, > > On Tue, 27 Nov 2007, しらいしななこ wrote: > >> Quoting Andreas Ericsson <ae@op5.se>: >> >>> "git pull --rebase" already has an implementation. Dscho cooked one up >>> which I've been using since then. It works nicely. >> What is the reason that the option was not added to the official git? >> Was it coded poorly, buggy or were there some other issues? > > It is very well possible that it was coded poorly ;-) > > The main reason, I believe, was that some old-timers who know the > implications said that it would encourage a wrong workflow.
If by "wrong", those old-timers meant "a workflow not commonly used in a published one-pushes-many-pulls repository", I certainly agree.
> 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".
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.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231