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 one of the least suckless pieces of software > I've ever worked with. It's complex, obscure, inconsistent, quirky... Bad style. Either tell what you did and how you came to your conclusion or skip the above paragraph. Git vs. hg was discussed here for some time so your statement is not obvious. What I'm telling you here on the other hand is obvious and probably all of us know what I'm trying to say here -- It's just a friendly reminder. Regards, Yoshi > > You migrated from hg to git, because *git* sucks less??? Say WHAT?!
Re: [dev][surf] fix DOWNLOAD macro cookies
Greetings. On Wed, 13 Feb 2013 06:49:59 +0100 Carlos Torres wrote: > Hello, > Attached you'll find a simple patch that makes the DOWNLOAD macro > use the cookiefile variable. Thanks, the patch is applied. Sincerely, Christoph Lohmann
[dev] [st] Limit refresh rate
This patch limit refresh rate by new (more efficient) way. Patch separate refresh in tree case: 1. app send something to terminal 2. we have XEvent 3. post XEvent In first case we can limit refresh to quite low rate (in patch 5 fps) to prevent useless overflow when app send to many text (progress in mc, compilation, ...). In second case we want have low latency (interactivity): when we press some key we want to see result. I limit this case to 30 fps. In third case we still want fast refresh for near time to see full output from app. Certainly, you can easy customize refresh rate as you wish. I also check and tune this patch with profiler. With limit 30fps I have two time lower cpu consumption (by each - st and xorg). With 5 fps it very low and I can't accurately measure it. st-refresh_rate.patch Description: Binary data
[dev] Suckless and Wayland
Hi guys, I already started a similar topic some months ago where I asked you your opinion. Now, the project seems to move fast, this is why I start another subject. The aim is different now, and I want to have some details from Suckless community / developpers about the upcoming technology. After reading many Wayland articles, I think it will completely change Linux ecosystem and I'm a bit worried. Wayland introduces fuzzy aspects and they're not very clear for me (POSIX compliant, KMS and network transparency). Since I like many softwares like dwm & st, I wonder how I'll do when Wayland will become the norm (as systemd). I really hope you consider porting your essentials softwares on Wayland, because major distribs like Fedora or Ubuntu plan to use it. I think it's a dilemma: using your work on non-Wayland distribs or dropping my favorites softwares for Wayland... Here my concerns (I'm not the only one, I guess). Best Regards.
Re: [dev] Suckless and Wayland
On 13/02/2013, Hugues Moretto-Viry wrote: > I already started a similar topic some months ago where I asked you your > opinion. > Now, the project seems to move fast, this is why I start another > subject. > The aim is different now, and I want to have some details from Suckless > community / developpers about the upcoming technology. > > After reading many Wayland articles, I think it will completely change > Linux ecosystem and I'm a bit worried. Well, what is its natural predator? > Wayland introduces fuzzy aspects and they're not very clear for me (POSIX > compliant, KMS and network transparency). > > Since I like many softwares like dwm & st, I wonder how I'll do when Wayland > will become the norm (as systemd). > I really hope you consider porting your essentials softwares on Wayland, I really hope we don't. > because major distribs like Fedora or Ubuntu plan to use it. They can use clay tablets for all I care. > I think it's a dilemma: using your work on non-Wayland distribs or dropping > my favorites softwares for Wayland... No dilemma here. > Here my concerns (I'm not the only one, I guess). The only one in this thread so far.
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 nonsense. It does not compare well to hg at all. Given the choice between a great core in C with an awful front end and ghastly documentation, and a good core with excellent front end, and written in python... I would have stuck with hg. I use git every day, have written tools to ease the pain of working with it, etc. I quite like it, I just don't see that it is even remotely suckless, unless you would rework all the front-end tools at least. The only sensible reason I can see for preferring git is that it doesn't depend on python. But, you'd rather use a sucky tool written in a supposedly suckless language, versus a suckless tool written in a supposedly sucky language? Perhaps if the git doc and help were less terrible ... Sam
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. Let's say you wanted to get rid of all history from a repo, just keep the current commit. Git lets us rewrite history, so this should be easy, right? Wrong. I won't tell you how long it took to find this weird technique: #!/bin/sh -e new_root_hash=`git rev-parse HEAD` echo "$new_root_hash" >.git/info/grafts git filter-branch -f rm .git/info/grafts At least it runs quickly. Let's say you want to garbage collect your repo after getting rid of that unwanted history... git gc whoops, it does not work. final hacky 'solution' (after quite some research and experiment): #!/bin/sh -ev git remote rm origin || true git for-each-ref --format="%(refname)" refs/original/ | xargs -n1 --no-run-if-empty git update-ref -d ( cd .git rm -rf refs/remotes/ refs/original/ *_HEAD logs/ ) git -c gc.reflogExpire=0 -c gc.reflogExpireUnreachable=0 -c gc.rerereresolved=0 -c gc.rerereunresolved=0 -c gc.pruneExpire=now gc "$@" But ordinary things are famously weird in git, also.
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, inconsistent, quirky... > > > tell what you did > > Ok, here is one day in the life of messing about with git. > > > Let's say you wanted to get rid of all history from a repo, just keep > the current commit. Git lets us rewrite history, so this should be > easy, right? Wrong. I won't tell you how long it took to find this > weird technique: > > #!/bin/sh -e > new_root_hash=`git rev-parse HEAD` > echo "$new_root_hash" >.git/info/grafts > git filter-branch -f > rm .git/info/grafts > > At least it runs quickly. > > > Let's say you want to garbage collect your repo after getting rid of > that unwanted history... > > git gc > > whoops, it does not work. > > final hacky 'solution' (after quite some research and experiment): > > #!/bin/sh -ev > git remote rm origin || true > git for-each-ref --format="%(refname)" refs/original/ | xargs -n1 > --no-run-if-empty git update-ref -d > ( > cd .git > rm -rf refs/remotes/ refs/original/ *_HEAD logs/ > ) > git -c gc.reflogExpire=0 -c gc.reflogExpireUnreachable=0 -c > gc.rerereresolved=0 -c gc.rerereunresolved=0 -c gc.pruneExpire=now gc "$@" > > > But ordinary things are famously weird in git, also. > > >
Re: [dev] Suckless and Wayland
There is nice new LWN coverage on Wayland here: http://lwn.net/Articles/536862/ Embrace change :)
Re: [dev] Suckless and Wayland
On Wed, Feb 13, 2013 at 07:20:10PM -0500, Strake wrote: > > because major distribs like Fedora or Ubuntu plan to use it. > > They can use clay tablets for all I care. there is no way any linux distro in the foreseeable future will drop support for Xlib, that would be ridiculous. If they use Weyland, there will have to be an X emulation library for it. That's all.
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 and Wayland
Greetings. On Thu, 14 Feb 2013 06:25:19 +0100 Hugues Moretto-Viry wrote: > Hi guys, > > I already started a similar topic some months ago where I asked you your > opinion. Now, the project seems to move fast, this is why I start another > subject. > The aim is different now, and I want to have some details from Suckless > community / developpers about the upcoming technology. > > After reading many Wayland articles, I think it will completely change > Linux ecosystem and I'm a bit worried. > Wayland introduces fuzzy aspects and they're not very clear for me (POSIX > compliant, KMS and network transparency). > > Since I like many softwares like dwm & st, I wonder how I'll do when > Wayland will become the norm (as systemd). > I really hope you consider porting your essentials softwares on Wayland, > because major distribs like Fedora or Ubuntu plan to use it. > I think it's a dilemma: using your work on non-Wayland distribs or dropping > my favorites softwares for Wayland... > > Here my concerns (I'm not the only one, I guess). Learn to code C, send in patches and help us in doing such a switch. Then you are able to change your own destiny without any worries. Sincerely, Christoph Lohmann
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 what you did
>
> Ok, here is one day in the life of messing about with git.
>
>
> Let's say you wanted to get rid of all history from a repo, just keep
> the current commit. Git lets us rewrite history, so this should be
> easy, right? Wrong. I won't tell you how long it took to find this
> weird technique:
>
> [...]
>
> But ordinary things are famously weird in git, also.
>
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 works perfectly fine after running that.
Re: [dev] Suckless and Wayland
On Thu, Feb 14, 2013 at 5:01 AM, Kai Hendry wrote: > There is nice new LWN coverage on Wayland here: > http://lwn.net/Articles/536862/ > > Embrace change :) > choke on paywalls. On Thu, Feb 14, 2013 at 6:25 AM, Christoph Lohmann <2...@r-36.net> wrote: [...] > > Learn to code C, send in patches and help us in doing such a switch. > Then you are able to change your own destiny without any worries. > this is what I expect from the people around here, too. :) cheers! mar77i
