On 11-05-2008, Stefano Zacchiroli [EMAIL PROTECTED] wrote:
--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, May 11, 2008 at 06:04:38PM +, Sylvain Le Gall wrote:
I would better recommend
:
On Sat, May 10, 2008 at 02:20:25PM +0200, Stéphane Glondu wrote:
BTW, what will be our plans for the migration?
Was I sure that we will *not* go for the 3.10.2 transition before Lenny
I would answer: let's do the git migration right away. Given that we are
probably going to have a 3.10.2
On Mon, May 12, 2008 at 09:24:02AM +, Sylvain Le Gall wrote:
Concerning the waste of time, i disagree. Git is not the final SCM
around. There will be other. Understanding git, darcs, tla, cvs, svni,
This was not the point of my waste of time, no praise to git was
intended. It is rather
On 12-05-2008, Stefano Zacchiroli [EMAIL PROTECTED] wrote:
On Mon, May 12, 2008 at 09:24:02AM +, Sylvain Le Gall wrote:
PS regarding asking questions I indeed liked the darcs default of
doing that. Git is lacking it, though in the most important cases you
have flags to trigger it.
On Sat, May 10, 2008 at 06:58:50PM +0200, Ralf Treinen wrote:
BTW, what would you suggest to read as an introduction into concurrent
version control systems and git? I have to admit that I am still
living in the cvs/svn age.
No problem, I was there not more than 6 months ago :-)
On the Git
On Sun, May 11, 2008 at 18:04:38 +, Sylvain Le Gall wrote:
I would better recommend beginning with darcs rather than git. They
share almost all principle, but darcs is more user friendly. Once you
have get the basic principle of DSCM (get/pull/push/...), you should go
to git.
I guess
On Sun, May 11, 2008 at 06:04:38PM +, Sylvain Le Gall wrote:
I would better recommend beginning with darcs rather than git. They
share almost all principle, but darcs is more user friendly. Once you
have get the basic principle of DSCM (get/pull/push/...), you should go
to git.
If your
Hello,
I've written (yet another) svn2git migration script¹ specialized for our
svn layout, that handles upstream branches.
¹
http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/tools/svn2git/glondu_svn2git.py?op=filerev=0sc=1
It successfully generated the following repos:
will *not* go for the 3.10.2 transition before Lenny
I would answer: let's do the git migration right away. Given that we are
probably going to have a 3.10.2 transition I would wait for that: I do
not want to waste people energy in learning a new tool *during* the
transition. Bottom line: I propose to do
On Sat, May 10, 2008 at 06:46:25PM +0200, Stefano Zacchiroli wrote:
On Sat, May 10, 2008 at 02:20:25PM +0200, Stéphane Glondu wrote:
BTW, what will be our plans for the migration?
Was I sure that we will *not* go for the 3.10.2 transition before Lenny
I would answer: let's do the git
10 matches
Mail list logo
