> -----Original Message-----
> From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On Behalf Of Alex Ionescu
> Sent: 15. november 2005 22:44
> To: ReactOS Development List
> Subject: Re: [ros-dev] RE: [ros-diffs] [cwittich] 19254: add a checkforSPDRP_CONFIGFLAGSwhich is
> not working yet
>> He abandonned his code and it needed a new maintainer. I think you're
> (purposedly) confusing "maintaining" and "owning" while trying to make a
> point which doesn't exist. Ge didn't agree with a change I made in
> Freeldr, and I reverted it. Why? Because he's maintaining it and I don't
> want to make his life hard. If Magnus spent 6 months writing a DX
> library from scratch, does that mean I can come in and rewrite half his
> code because I don't like it? No it doesn't. As the maintainer and guy
> that wrote 100% of the library he should have a choice in design
> decisions made with it. That doesn't mean he has to be Hitler, but it
> does give him some authority over his own code.
Any developer can argue for/against a change, so why make the distinction
between owner and non-owner? I would sleep so much better at night if the
reason you reverted the freeldr change was that Gé provided a sound
technical argument against the change (have to build, test and distribute
different .isos for different sub-architectures, only to save a few bytes
in the freeldr/setupldr binaries) and not because he was maintaining freeldr.
Maintainers come and go. The source code stays.
> >There is very much a point in reviewing as early as possible. It is to find
> >bugs as early as possible.
> >
> >
> I agree and never said anything against this.
>
Ok, maybe I interpreted it wrong. Maybe you or someone else could explain how
the following should be interpreted then?
"It's why I now run a local branch and only commit final code; it lets me do what I want with code that I wrote 100% of, without
being criticzed about design choices before the application is complete."
Note that I'm not against local branches at all. What I care about is what
and how changes get into the ReactOS repository.
> >Casper
> >
> >
> Sometimes I think you like to invent things just to have something to
> say. I never said that "I'm afraid to answer questions" or that
> "Reviewing is only about critiquing". I pointed out that I find it
> stupid and wasteful to make community decisions on something that the
> writer hasn't done yet! Imagine a program or DLL as being a book. It
> starts out in 3 phases
>
And I argue that it is not stupid and wasteful. It gives more developers
a chance to comment on other developers work. Other developers may have
experience that may be beneficial in the development of that particular
feature. Other developers may have knowledge of another corner of ReactOS
where similar code exists and code could be shared. Other developers may
see problems with the direction the developer is going and could bring it
to the attention of the developer before going a thousand miles in a
"bad" direction. Other developers may have experience that could add to
achieving a better solution. Holding off the commit/review, decreases the
usefulness of the distributed nature of the development of ReactOS.
> 1) Manuscript being written. At this moment, entire sentences are added
> and removed, sometimes 3, 4 times in a row until the author decides what
> to do. Entire chapters can disappear. Plot twists can be removed or added.
> 2) Manuscript is written. The author is happy with his work and thinks
> its mostly complete. His editor and publisher will now do reviews, which
> can still result in modifications present in the book, sometimes even
> major. Sometimes the author might not agree, but usually they are team
> decisions, and many times it's mistakes that the author himself hadn't
> noticed
> 3) Published book.
Maybe if the editor was brought in from the start, he could have prevented
wasting time on writing those sections just to remove them later.
> you're a top-down developer. It might only work for people that have
> already thought of the design for entire months, and start out with
> their DllMain and then write the 100 stubs they know they will need. But
> most developers don't do that; some are not aware of the potential
> issues which might arise.
There is no need to think about the entire design. You just set a goal for
each commit that will bring the software one step closer to where you want
it to be. Be it preparing for something by refactoring the existing code,
adding or deleting code or something entirely different. The important
thing is to try to have it work better or at least just as good as before
the commit.
> You can have developed your whole program,
> only to realize it fails miserable on MP platforms because you never
> tested. And this kind of mistake happens even to the best programmers,
> sometimes years later. Look at the Audio subsystem in NT. It was
> rewritten THREE times, going from 2/3 user mode 1/3 kernel mode to 1/2
> user mode 1/2 kernel mode to 100% user mode in Vista. And we're talking
> about a company with dedicated teams and years of experience to find
> these kinds of design flaws. But it still took them 15 years to realize
> it. So don't tell me that a coder can't realize a mistake after only a
> month of testing.
I don't see what you are arguing for/against here.
Casper
More information about the Ros-dev
mailing list
CHAPTER VII. THE FOUR CLASSES OF SOCIETY. THE FOUR CLASSES OF SOCIETY. "After the herald had given the names of the wrestlers who were to make the first round, the fellows came in. They were dressed without any clothes to speak of, or rather they were quite undressed, with the exception of a cloth around their loins. They came in on opposite sides of the ring, and stood there about five feet apart, each man resting his hands on his knees, and glaring at the other like a wild beast. They[Pg 231] looked more like a pair of tigers than human beings, and for a moment I thought it was not at all unlike what a bull-fight in Spain might be. I turned upon her choking with anger, but her melting beauty rendered me helpless. Black woods were on our left. "Shall we turn in here?" I asked. "None of that with me," he growled. "Do you know who I am, Countess Lalage? I am Leon Lagage, Count of the Holy Roman Empire, and your husband. Incomparable woman, you cannot alter that fact. For better or worse, for richer or poorer, till death do us part!" I have in this way imperfectly indicated a methodical plan of generating a design, as far as words alone will serve, beginning with certain premises based upon a particular work to be performed, and then proceeding to consider in consecutive order the general character of the machine, mode of operation, movements and adjustments, general arrangement, strains, special arrangement, and proportions. ‘Alas! what is life, what is death, what are we, 11th January two best dresses. Commencement was as usual, with a few showers “All right,” agreed Sandy. “Dick, you and I are the ground crew. As soon as you’re ready, Mr. Whiteside, we’ll take hold!” Effects of Walpole's Administration—Formation of the new Ministry—Attitude of the Malcontents—Committee of Inquiry into Walpole's Administration—Walpole's Protectors—Ministerial Measures—Prorogation of Parliament—Disasters of the French—British Division in the Netherlands—Opening of Parliament—The German Mercenaries—Amendment of the Gin Act—George goes to Germany—Stair and De Noailles in Franconia—Stair in a Trap—Bold Resolution of King George—The Battle of Dettingen—Resignation of Stair—Retreat of the French—Negotiations for Peace—Treaty of Worms—Pelham becomes Prime Minister—The Attacks of Pitt on Carteret—Attempted Invasion of England—Its Failure—Progress of the French Arms—Frederick II. invades Bohemia—His Retirement—Resignation of Carteret—Pelham strengthens his Ministry—Death of the Emperor—Campaign in Flanders—Battle of Fontenoy—Campaign of Frederick II.—The Young Pretender's Preparations—Loss of the Elizabeth—Landing in the Hebrides—The Highland Clans join him—The First Brush—Raising of the Standard—Cope's Mistake—He turns aside at Dalwhinnie—Charles makes a Dash for Edinburgh—The March to Stirling—Right of the Dragoons—The "Canter of Coltbridge"—Edinburgh surprised by the Highlanders—Charles marching against Cope—Battle of Prestonpans—Delay in marching South—Discontent of the Highland Chiefs—The Start—Preparations in England—Apathy of the Aristocracy—Arrival of the Duke of Cumberland—Charles crosses the Border—Capture of Carlisle—The March to Derby—Resolution to retreat—"Black Friday"—The Retreat—Recapture of Carlisle—Siege of Stirling—Battle of Falkirk—Retreat to the Highlands—Cumberland's Pursuit—Gradual Collapse of the Highlanders—Battle of Culloden—Termination of the Rebellion—Cruelty of the Duke of Cumberland—Adventures of the Young Pretender—Trials and Executions—Ministerial Crisis. The next morning he was up betimes, and cooked the boys as good a breakfast as he could out of the remainder of his store and what he could get from the hospital, and then gave what was left to whoever came. The comfortable crib, which had cost the Deacon so much labor, had been pre-empted by the Surgeon for some of his weakest patients. "You two step forward one pace," he commanded. "Gentleman, I've got my six. The rest are yours." "Where are you goin'?" he said sternly. Every now and then the crowd would break into the latest rhymings of MacKinnon's poet: A large thicket, at this moment, gave the dusty foot an opportunity of doubling, and, for an instant, diverging from the straightforward course, though it availed him little, he seemed to feel the breath of his pursuer on the back of his neck; his foot sounded as if at his heels; he drew his garment closely around him, turned suddenly to the right, and, bounding from the ground, the next instant a splash was heard in the little river, and the fugitive was safe from his pursuer. HoME明日之后怎么免费刷一级纳米材料
ENTER NUMBET 0018moubi.com.cn chepingo.com.cn yunhaitea.com.cn xhpq.com.cn zengyuyu.com.cn b041.com.cn fuchents.com.cn oujl.com.cn nk86.com.cn www.cpgz607.com.cn