Re: [dev] [suckless] Migration to git

On Thu, Feb 14, 2013 at 07:24:28AM +0100, Lukas Fleischer wrote: > It's a one-liner: > > $ git reset $(git commit-tree -m "foobar" HEAD^{tree}) > > Pretty fast: > > git reset $(git commit-tree -m "foobar" HEAD^{tree}) 0.00s user 0.01s > system 70% cpu 0.009 total > > `git gc` also wor

Re: [dev] [suckless] Migration to git

On Thu, Feb 14, 2013 at 01:01:03PM +1100, Sam Watkins wrote: > > I've been working with git lately, trying to do some unusual things, > > and I need to say this is one of the least suckless pieces of software > > I've ever worked with. It's complex, obscure, inconsistent, quirky... > > > tell wha

Re: [dev] [suckless] Migration to git

On Thu, Feb 14, 2013 at 11:07:36AM +0800, Chris Down wrote: > Are you kidding me? Are you unaware of git rebase? git rebase is slower and does not always work, I don't really want to go into the gory details

Re: [dev] [suckless] Migration to git

Are you kidding me? Are you unaware of git rebase? On 14 February 2013 10:01, Sam Watkins wrote: > > I've been working with git lately, trying to do some unusual things, > > and I need to say this is one of the least suckless pieces of software > > I've ever worked with. It's complex, obscure,

Re: [dev] [suckless] Migration to git

> I've been working with git lately, trying to do some unusual things, > and I need to say this is one of the least suckless pieces of software > I've ever worked with. It's complex, obscure, inconsistent, quirky... > tell what you did Ok, here is one day in the life of messing about with git.

Re: [dev] [suckless] Migration to git

On Wed, Feb 13, 2013 at 12:56:44AM +0100, Jens Nyberg wrote: > People who can not grasp git thinks it's bad, it's that simple. The git core is really very good and even almost suckless. The git front end is very functional and capable, but also a catastropic chaos of bolted on inconsistent nonsen

Re: [dev] [suckless] Migration to git

Am Wed, 13 Feb 2013 10:28:26 +1100 schrieb Sam Watkins : > On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: > > I am proposing a migration of all mercurial to git repositories. > > I've been working with git lately, trying to do some unusual things, > and I need to say this is o

Re: [dev] [suckless] Migration to git

To be fair I think there are a multitude of ways in which git is less sucky than hg: - multiple binaries - significantly more modular design framework - doesn't assume the user is an idiot (which is probably why so many people have problems with it) - there are plenty of things of *daily use* in g

Re: [dev] [suckless] Migration to git

My mother was actually not pleased when she used git. She liked the idea of a suck less frontend though. Wolfgang On Feb 12, 2013 6:57 PM, "Jens Nyberg" wrote: > 2013/2/13 Chris Down : > > Care to give some examples of where git sucks more than hg? I've found it > > particularly un-sucky, but no

Re: [dev] [suckless] Migration to git

2013/2/13 Chris Down : > Care to give some examples of where git sucks more than hg? I've found it > particularly un-sucky, but non-intuitive in places. > People who can not grasp git thinks it's bad, it's that simple. Irony of it all is that it is actually a very simple design that is both fast,

Re: [dev] [suckless] Migration to git

Care to give some examples of where git sucks more than hg? I've found it particularly un-sucky, but non-intuitive in places. On 13 February 2013 07:28, Sam Watkins wrote: > On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: > > I am proposing a migration of all mercurial to git

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: > I am proposing a migration of all mercurial to git repositories. I've been working with git lately, trying to do some unusual things, and I need to say this is one of the least suckless pieces of software I've ever worked with.

Re: [dev] [suckless] Migration to git

On Mon, 26 Nov 2012 17:08:56 +0100 "Roberto E. Vargas Caballero" wrote: > It is due to git keeps the api in small programs than you could use in your > scripts. These small programs are 100% Unix philosophy (do only one thing and > do it fine, write an output that can be used as input for other,

Re: [dev] [suckless] Migration to git

I don't think using git will solve anything because there's no problem to solve. That being said, I don't mind using either git or mercurial. The official repo should stay on suckless.org, though.

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 4:36 PM, Comrade DOS wrote: > Hi. > Migration on git is a very good idea. Maybe you can move source code on > github and/or bitbucket? Yes it's a very good idea. Lets migrate everything to the One True Church of Github.

Re: [dev] [suckless] Migration to git

Hi there, I discussed with 20h on IRC. I agreed with him to investigate all necessary steps for such a switch and to bring everything in place. Then we can estimate and dry-run if this is any worth. This decision is just because of the fact that 20h is the most active contributor -- and that the

Re: [dev] [suckless] Migration to git

On 27 November 2012 18:57, Anselm R Garbe wrote: > On 26 November 2012 11:25, Christoph Lohmann <2...@r-36.net> wrote: >> I am proposing a migration of all mercurial to git repositories. Git is >> mature and used by nearly all major OSS projects. Mercurial has this >> slow prototyping depen

Re: [dev] [suckless] Migration to git

On 27 November 2012 12:43, Raphael Proust wrote: > On Tue, Nov 27, 2012 at 10:36 AM, markus schnalke wrote: >> It's the ingenuity of Unix to have just one kind of fork(). Why can't >> we map this concept to DVCS and have just one kind of cloning? > > darcs? > > (Yes, I know, it's not written in C

Re: [dev] [suckless] Migration to git

Hi 20h, On 26 November 2012 11:25, Christoph Lohmann <2...@r-36.net> wrote: > I am proposing a migration of all mercurial to git repositories. Git is > mature and used by nearly all major OSS projects. Mercurial has this > slow prototyping dependency of Python, which is annoying and could

Re: [dev] [suckless] Migration to git

Greetings. On Tue, 27 Nov 2012 18:24:47 +0100 Comrade DOS wrote: > Hi. > Migration on git is a very good idea. Maybe you can move source code on > github and/or bitbucket? Github and Bitbucket promote half‐done projects without the basic struc‐ ture of some LICENSE, README and Makefile. At least

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 10:36:38PM +0700, Comrade DOS wrote: > Hi. > Migration on git is a very good idea. Maybe you can move source code on > github and/or bitbucket? Do you want ants, Christoph? Because this is how you get ants.

Re: [dev] [suckless] Migration to git

Hi. Migration on git is a very good idea. Maybe you can move source code on github and/or bitbucket?

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 3:10 PM, Barbu Paul - Gheorghe wrote: > On 11/27/2012 02:50 PM, Strake wrote: > Hello, > > >> Darcs has no history edition, as it essentially keeps no history, >> which is a win in my book. The main difficulty seems to be the >> corner-case exponential-time merge algorithm.

Re: [dev] [suckless] Migration to git

On 11/27/2012 02:50 PM, Strake wrote: Hello, Darcs has no history edition, as it essentially keeps no history, which is a win in my book. The main difficulty seems to be the corner-case exponential-time merge algorithm. I'm not familiar with that VCS, but how can it store no history since tha

Re: [dev] [suckless] Migration to git

Greetings. On Tue, 27 Nov 2012 14:43:35 +0100 hiro <23h...@gmail.com> wrote: > On Tue, Nov 27, 2012 at 2:15 PM, Christoph Lohmann <2...@r-36.net> wrote: > > But in the meanwhile the migration to git can be done easily > > are you willing to back this claim with money? Of course not. It’s unreli

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 2:15 PM, Christoph Lohmann <2...@r-36.net> wrote: > But in the meanwhile the migration to git can be done easily are you willing to back this claim with money?

Re: [dev] [suckless] Migration to git

Greetings. On Tue, 27 Nov 2012 14:15:43 +0100 Hadrian Węgrzynowski wrote: > As Kurt asked earlier - what for? Because it sucks a bit less? I'm more > git user myself, but hg is OK. Even if git sucks less, so what? Well, this is »suckless« so things that »suck less« are adopted. There was the

Re: [dev] [suckless] Migration to git

On Mon, 26 Nov 2012 11:25:18 +0100 Christoph Lohmann <2...@r-36.net> wrote: > Greetings comrades, > > I am proposing a migration of all mercurial to git repositories. Git > is mature and used by nearly all major OSS projects. Mercurial > has this slow prototyping dependency of Python, whic

Re: [dev] [suckless] Migration to git

On 27/11/2012, Raphael Proust wrote: > darcs? > > (Yes, I know, it's not written in C. The interface is very clean > though. There is no branching, no history rewritting, no bells and > whistles.) It's not in C, but Haskell code can be easily compiled and distributed in binary form. Darcs has no

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 10:36 AM, markus schnalke wrote: > It's the ingenuity of Unix to have just one kind of fork(). Why can't > we map this concept to DVCS and have just one kind of cloning? darcs? (Yes, I know, it's not written in C. The interface is very clean though. There is no branching,

Re: [dev] [suckless] Migration to git

[2012-11-27 12:03] chris hall > On Tue, Nov 27, 2012 at 8:50 AM, markus schnalke wrote: > > [2012-11-26 16:47] "Roberto E. Vargas Caballero" > > > - History rewriting: git rebase or git filter-branch > > (btw: That's the worst feature a version control system can offer.) > > I disagree, IMO

Re: [dev] [suckless] Migration to git

On Tue, Nov 27, 2012 at 8:50 AM, markus schnalke wrote: > [2012-11-26 16:47] "Roberto E. Vargas Caballero" > > - History rewriting: git rebase or git filter-branch > (btw: That's the worst feature a version control system can offer.) I disagree, IMO this is one of the most useful features of

Re: [dev] [suckless] Migration to git

[2012-11-26 16:47] "Roberto E. Vargas Caballero" > > [...] but if > you want some reasons I am going to give you some of then: > > - History rewriting: git rebase or git filter-branch (btw: That's the worst feature a version control system can offer.) > - Mail workflow support: git am,

Re: [dev] [suckless] Migration to git

On 11/26/2012 12:25 PM, Christoph Lohmann wrote: Greetings comrades, Hello! I am proposing a migration of all mercurial to git repositories. Git is mature and used by nearly all major OSS projects. Mercurial has this slow prototyping dependency of Python, which is annoying and could b

Re: [dev] [suckless] Migration to git

* pancake [2012-11-26 18:00]: On 11/26/12 17:33, Kurt H Maier wrote: programming languages, and pretending it's 'simple' because it's broken sloccount git = 126.000 C libgit2 = 37.000 mercurial = 34.000 python + 3000 in C if you say that python loc is 2x times the same done in C then we sho

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 05:55:33PM +0100, pancake wrote: > about hgfs... it is using the mercurial python module, right? because > the googlecode svn repo is empty.. or am i pointing to the wrong hgfs? cinap's done a lot of work removing dependencies on the python/ape stuff. it's not 100% there

Re: [dev] [suckless] Migration to git

On 11/26/12 17:33, Kurt H Maier wrote: programming languages, and pretending it's 'simple' because it's broken sloccount git = 126.000 C libgit2 = 37.000 mercurial = 34.000 python + 3000 in C if you say that python loc is 2x times the same done in C then we should move to libgit2 with a decen

Re: [dev] [suckless] Migration to git

Somebody claiming to be Kurt H Maier wrote: It's like c++: "everyone agrees it's safe to use, but nobody agrees on which 10% is the safe part." I think we call that part of C++ "C89". (Roughly, modulo valid C89 that C++ makes invalid.) -- Stephen Paul Weber, @singpolyma See

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 05:29:23PM +0100, Roberto E. Vargas Caballero wrote: > > I am going to stop this discussion because I think we will not gain anything > with it, but it is very funny that people here use the word 'complex' in some > religious way, and the things that they don't like directl

Re: [dev] [suckless] Migration to git

git flags are crap using getoptlong, i always wondered why nobody did a saner (hg like) frontend for git (maybe using libgit2?) and using only one letter flags . also i would support any mercurial rewrite in C, but mercurial people will probably laught on you. i also tried once to simplify the s

Re: [dev] [suckless] Migration to git

> All you've done is convince me that git is its own operating system. > It's ludicrously complex and needlessly huge. I don't care that it is > trendy or popular with developers; most of the 'benefits' you listed are > basically using git as though it were an entire disk filesystem. I am going

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 05:08:56PM +0100, Roberto E. Vargas Caballero wrote: > > The git source tree is more than four hundred percent bigger than the > > are you comparing the size of a project in python with the size of a project > written in C?. The logical relation should be 2 times the size o

Re: [dev] [suckless] Migration to git

2012/11/26 Roberto E. Vargas Caballero : > - History rewriting: git rebase or git filter-branch mq does this > - Mail workflow support: git am, git format-patch or git email. patchbomb? > - Incremental commits: git add -i, git checkout -f. > - A diary of tip references: git reflog

Re: [dev] [suckless] Migration to git

> The git source tree is more than four hundred percent bigger than the are you comparing the size of a project in python with the size of a project written in C?. The logical relation should be 2 times the size of hg, and then you could say that they have a similar size. > mercurial source tree.

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 10:38:17AM -0500, Calvin Morrison wrote: > One could argue that hg doesn't fit the suckless philosophy The git source tree is more than four hundred percent bigger than the mercurial source tree. git ships more than 160 *man pages*. It is the emacs of version control. Th

Re: [dev] [suckless] Migration to git

> if we're going to change vcs just to change, why not move back to darcs > or something? I'm still waiting for anyone to make any kind of case for > changing to git other than "lots of people use it." I don't matter if the repositories change or not, I am using git now, but if you want some reas

Re: [dev] [suckless] Migration to git

On 26 November 2012 10:26, Kurt H Maier wrote: > On Mon, Nov 26, 2012 at 04:10:46PM +0100, pancake wrote: > > On 11/26/12 15:41, Kurt H Maier wrote: > > everytime i proposed in mercurialchan to rewrite it in C, everybody > > thought i was trolling or so.. i would also love to have hg in c, > > bu

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 04:10:46PM +0100, pancake wrote: > On 11/26/12 15:41, Kurt H Maier wrote: > everytime i proposed in mercurialchan to rewrite it in C, everybody > thought i was trolling or so.. i would also love to have hg in c, > but the reactions were pretty rude, so i decided to move to g

Re: [dev] [suckless] Migration to git

Right, but python is also an interpreted language, so you need to have the python runtime installed. With other revision control systems I can ( in theory ) distribute a standalone, static linked binary without having to deal with any deps. On 26 November 2012 10:10, pancake wrote: > On 11/26

Re: [dev] [suckless] Migration to git

On 11/26/12 15:41, Kurt H Maier wrote: On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: I am proposing a migration of all mercurial to git repositories. Git is mature and used by nearly all major OSS projects. Mercurial has this slow prototyping dependency of Python, wh

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 11:55:39AM +0100, Roberto E. Vargas Caballero wrote: > > Uhmm, I have done it with st repository of course, I work with git against > the actual hg repository ^^!!!. > Christoph, why can't you just do this instead of shitting all over everything else?

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: > I am proposing a migration of all mercurial to git repositories. Git is > mature and used by nearly all major OSS projects. Mercurial has this > slow prototyping dependency of Python, which is annoying and could be > remov

Re: [dev] [suckless] Migration to git

> I am proposing a migration of all mercurial to git repositories. not sure if really bored or biten by rabid linux hipster

Re: [dev] [suckless] Migration to git

> the following instructions depend on hggit module being installed > and enabled > in hgrc. fyi > > export hg repo to github > > $ hg log | grep ^user |sort -u | sed -e 's, ,\t,g' |awk '{print > $2="pancake "}' > map > $ vim map # remove user: and set=value > $ hg convert

Re: [dev] [suckless] Migration to git

> I am proposing a migration of all mercurial to git repositories. Sounds good to me. I love git, and use it everywhere else. The interface is fine once you're used to it, and given that it's so much more widely used than hg, more people will probably be familiar with it than mercurial anyway. >

Re: [dev] [suckless] Migration to git

i use git in my phone and i dont even have perl in it. actually you have cgit and git and libgit2, both implementations are in C and have no extra dependencies of scripting languages (at runtime), maybe at build.. that's why i decided to get rid of mercurial. i had some problems because of the cr

Re: [dev] [suckless] Migration to git

måndagen den 26 november 2012 11.48.09 skrev Roberto E. Vargas Caballero: > > Perl dependency in git is present only in no basic commands. You can remove > it and the core system will follow working. does anyone have experience with libgit2 ? It seems to be pure C and only depend on zlib. I

Re: [dev] [suckless] Migration to git

> > Dpb on IRC showed me [0], which seems to do a near to perfect import of > > the old hg history. Anyone had bad experiences with this? > > I have experience with git and importing others vc to it, but I have never > done it with Mercurial. > Uhmm, I have done it with st repository of course, I

Re: [dev] [suckless] Migration to git

On Mon, Nov 26, 2012 at 11:25:18AM +0100, Christoph Lohmann wrote: > Greetings comrades, > > I am proposing a migration of all mercurial to git repositories. Git is > mature and used by nearly all major OSS projects. Mercurial has this > slow prototyping dependency of Python, which is annoy

[dev] [suckless] Migration to git

Greetings comrades, I am proposing a migration of all mercurial to git repositories. Git is mature and used by nearly all major OSS projects. Mercurial has this slow prototyping dependency of Python, which is annoying and could be removed that way. Of course git is still(?) adding a perl d