Hi All.
Giacomo Tesio pretty much expressed the flow. For me, the cheap
branching and excellent merging are extremely important, esp. as
compared with earlier systems like subversion.
The distribution development is also a huge boon; I have several
contributors with write access to the main git
zsh: cd $git-sources
zsh: wc -l **/*.{c,h,sh,py,pl}|tail -1
318901 total
zsh: for a in c h sh py pl; do echo $a: `wc -l **/*.$a|tail -1`;done
c: 161667 total
h: 16971 total
sh: 133214 total
py: 5634 total
pl: 1415 total
Is all that even necessary?
Dulwich is a 100%-complete pure-Python implementation of the Git API, which
optional C extensions for speed. It comes with a simple Git driver remake
that implements the core necessities, a.k.a. it has fetch-pack but no push
and send-pack but no pull. It would still pro
Actually, Jeff I appreciate a lot your work on mercurial. I know I could
use the bookmarks extension to achieve a similar process with hg (never
tried darcs and bzr seriously, sorry). but I still prefer git to mercurial,
since it has been designed around the features that I like (when working
alone
this world sucks
> On Mar 30, 2015, at 4:55 AM, Giacomo Tesio wrote:
>
> Ah, a small addendum: obviously we also use tags a lot to give a specific
> commit (and related history) a name.
> This is done automatically by build servers for the "official" tags, and
> manually by developers whenever they want in the
Ah, a small addendum: obviously we also use tags a lot to give a specific
commit (and related history) a name.
This is done automatically by build servers for the "official" tags, and
manually by developers whenever they want in their own repository (often
with tags like, "workedhere", "shittorefac
As I use both git and hg, I really miss the feature-branching in hg
(obviously, you can, if you try hard enough, use feature branching with hg
too, but git makes it so easy that it became my default process whenever I
can use git for development, even on solo projects):
Suppose you have a team of
