[Info-vax] Where to locate software

[Paul Sture]

On 2016-06-16, Craig A. Berry <craigberry at nospam.mac.com> wrote:
> On 6/16/16 10:09 AM, Johnny Billquist wrote:
>> On 2016-06-16 15:33, Craig A. Berry wrote:
>>> On 6/16/16 4:24 AM, Johnny Billquist wrote:
>>>
>>>> The distinction between committing and publishing on the other hand is
>>>> not really anything that impress me. It's more a crutch for people who
>>>> are afraid to commit.
>>>
>>> People should be afraid to commit. They should review and revise their
>>> code, make sure it passes tests, add more tests, reread and edit their
>>> commit messages, think about the order and coherence of the commits
>>> (changesets) and whether they preserve bisectability, all before
>>> considering the code finished and ready to publish.
>>
>> That is something I totally disagree with. The whole point of version
>> control systems is so that you can do changes and easily go back and
>> forth between versions, and if you did something wrong it is not a
>> catastrophe. Your attitude really reflects the pre VC era.
>
> What I said above was in the context of a centralized VCS making commit
> and push the same operation. With a DVCS you can commit early and commit
> often and use the VCS to manage multiple ongoing experiments and "go
> back and forth between versions" all you want. Of course you can share
> any of these at any stage with others via multiple different methods if
> and when you choose to. But you aren't forced by the tool to inflict
> them on everyone as soon as you create a changeset.

With a DVCS I've come across the concept of doing a commit 'just before
lunch' simply as a way of marking a point where you are leaving off for
a while.  Such commits are purely for the developer's convenience and
can/should later be merged into a larger commit which reflects a logical
and coherent code change versus points of time such as 'lunch' or 'going
home'.

"Combining Multiple Commits Into One Prior To Push"

<http://stackoverflow.com/questions/5721566/combining-multiple-commits-into-one-prior-to-push>

 

-- 
There are two hard things in computer science, and they are cache invalidation,
naming, and off-by-one errors.