[Cuis] Compose a Cuis distribution from *.pck files? (was Re: [Fwd: Re: [squeak-dev] Squeaksource, Squeak and Pharo..])

[H. Hirzel]

Sorry, the last two mails should have gone under the 'Learning git'
subject line.

As for building a Cuis distribution from *.pck files I think we need a
'packages' and a 'scripts' directory in the main repository

https://github.com/jvuletich/Cuis

And as we are at adding directories...
   in addition a 'documentation' directory

--Hannes

On 12/31/12, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> and later
>
> <citation>
> Because a branch in Git is in actuality a simple file that contains
> the 40 character SHA-1 checksum of the commit it points to, branches
> are cheap to create and destroy. Creating a new branch is as quick and
> simple as writing 41 bytes to a file (40 characters and a newline).
>
> This is in sharp contrast to the way most VCS tools branch, which
> involves copying all of the project’s files into a second directory.
> This can take several seconds or even minutes, depending on the size
> of the project, whereas in Git the process is always instantaneous.
> Also, because we’re recording the parents when we commit, finding a
> proper merge base for merging is automatically done for us and is
> generally very easy to do. These features help encourage developers to
> create and use branches often.
> </citation>
>
> Angel,
>
> how do you think we should use branches?
>
> Amber https://github.com/NicolasPetton/amber (Smalltalk which compiles
> to JavaScript and runs on node.js or in a browser) for example only
> has 5.
>
>
> --Hannes
>
> On 12/31/12, H. Hirzel <hannes.hirzel at gmail.com> wrote:
>> There are about 40 branches with names like 'Seaside', 'Omnibrowser',
>> 'Filesystem' ....
>>
>> and the tags are used for version numbers.
>>
>> It seems that the integration/development of a subsystem is done in a
>> branch.
>>
>> I think we all have to read Chapter 3 of the git book
>>
>> http://git-scm.com/book/en/Git-Branching
>>
>> <citation>
>> Some people refer to the branching model in Git as its “killer
>> feature” , and it certainly sets Git apart in the VCS community. Why
>> is it so special? The way Git branches is incredibly lightweight,
>> making branching operations nearly instantaneous and switching back
>> and forth between branches generally just as fast. Unlike many other
>> VCSs, Git encourages a workflow that branches and merges often, even
>> multiple times in a day. Understanding and mastering this feature
>> gives you a powerful and unique tool and can literally change the way
>> that you develop.
>> </citation>
>>
>> :-)
>>
>> --Hannes
>>
>>
>> On 12/31/12, Juan Vuletich <juan at jvuletich.org> wrote:
>>> Can you elaborate? You see here something I don't get.
>>>
>>> Thanks,
>>> Juan Vuletich
>>>
>>> Angel Java Lopez wrote:
>>>> Interesting... see the combination of tags and branches
>>>>
>>>> On Sun, Dec 30, 2012 at 6:53 PM, H. Hirzel <hannes.hirzel at gmail.com
>>>> <mailto:hannes.hirzel at gmail.com>> wrote:
>>>>
>>>>     And I think it is useful to have a look at the directory structure
>>>> of
>>>>        https://github.com/bonzini/smalltalk (GNU Smalltalk)
>>>>
>>>>     --Hannes
>>>>
>>>
>>>
>>> _______________________________________________
>>> Cuis mailing list
>>> Cuis at jvuletich.org
>>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>>
>>
>