Maybe it would be easier if we just write our own suckless git frontend using
libgit2. Without getoptlong and other monsters.
Just design a suckless workflow and implement it in a suckless tool.
I guess this tool can be also written in shellscript as a wrapper to git.
Btw, nobody commented this
you can still use mercurial, with it's hg-git extension, I sometimes
had small problems with it on huge repositories at work, never had any
problem with open source projects (maybe it's the size or less of 'do
whatever' attitude)
Pozdrawiam,
Łukasz Gruner
2012/11/29 Barbu Paul - Gheorghe :
> On 1
On Thu, Nov 29, 2012 at 06:18:25PM +0100, pancake wrote:
> definitively, git sucks
I could have told you that! lol
Mercurial is obviously much, much cleaner and simpler than git.
There's a reason why the suckless / cat-v / bell / google guys are using it.
Oh, wait...
The basic git system is rea
* Hugues Moretto-Viry [2012-11-29 22:34]:
> I really liked RSS feed with hg.
Just use: http://git.suckless.org/sites/atom.
> Thanks a lot.
> Regards
Cheers
Jochen
I really liked RSS feed with hg.
Could you create a feed with git as explained here (or with an other tool):
https://github.com/scotchi/gitfeed
Thanks a lot.
Regards
On 11/29/2012 09:47 PM, Rob wrote:
I imagine you can keep your own local branch, and rebase it upon
suckless' master branch, when it changes.
Cheers,
Rob
That's what I'll do I think.
--
Barbu Paul - Gheorghe
Common sense is not so common - Voltaire
Visit My GitHub profile to see my open-sour
On Thu, Nov 29, 2012 at 09:33:23PM +0200, Barbu Paul - Gheorghe wrote:
> On 11/29/2012 02:25 AM, Christoph Lohmann wrote:
> Now I have a question:
>
> How can be patches for dwm be managed via git?
> I mean I need a patch queue somehow, I'm thinking branches, I'll
> create a local branch with my pa
> How can be pathes for dwm be managerd via git?
> I mean I need a patch queue somehow, I'm thinking branches, I'll
> create a local branch with my patches applied and I will hack
> through its history.
I usually work in this way. After generate the patch sequence I get the diff
with git format-p
On 11/29/2012 02:25 AM, Christoph Lohmann wrote:
Greetings comrades,
Hello!
the migration to git is nearly complete. What’s missing is your tests
that everything works as expected.
Now I have a question:
How can be pathes for dwm be managerd via git?
I mean I need a patch queue somehow
I have applied this command to the repository of st:
git filter-branch --msg-filter '
sed "1 s/$/\\n/"'
This command restores the empty line after the first line in the commit
message.
You can see the difference between both history with:
git log --oneline
I
Christoph Lohmann <2...@r-36.net> writes:
> Greetings.
>
> On Thu, 29 Nov 2012 17:59:57 +0100 Christian Neukirchen
> wrote:
>> pancake writes:
>>
>> > the http support in git is a hack. are you guys running "git
>> > update-server-info"
>> > after every commit? this is used to update the http i
definitively, git sucks
On 11/29/12 17:59, Christoph Lohmann wrote:
Greetings.
On Thu, 29 Nov 2012 17:59:57 +0100 Christian Neukirchen
wrote:
pancake writes:
the http support in git is a hack. are you guys running "git
update-server-info"
after every commit? this is used to update the htt
Greetings.
On Thu, 29 Nov 2012 17:59:57 +0100 Christian Neukirchen
wrote:
> pancake writes:
>
> > the http support in git is a hack. are you guys running "git
> > update-server-info"
> > after every commit? this is used to update the http information with
> > the .git
> > database..
>
> man g
pancake writes:
> the http support in git is a hack. are you guys running "git
> update-server-info"
> after every commit? this is used to update the http information with
> the .git
> database..
man githooks:
> When enabled, the default post-update hook runs git update-server-info
> to keep the
the http support in git is a hack. are you guys running "git
update-server-info"
after every commit? this is used to update the http information with the
.git
database..
On 11/29/12 15:20, Daniel Bainton wrote:
On 29 November 2012 16:19, Nick wrote:
On Thu, Nov 29, 2012 at 02:15:36PM +,
On 29 November 2012 16:19, Nick wrote:
> On Thu, Nov 29, 2012 at 02:15:36PM +, Anthony Cox wrote:
>> On 29/11/12 14:01 ;+, Nick wrote:
>> >One thing is that there don't appear to be any tags (at least with
>> >surf, which is what I tested).
>>
>> Seems to work fine for me:
>>
>> >tony@morp
On Thu, Nov 29, 2012 at 02:15:36PM +, Anthony Cox wrote:
> On 29/11/12 14:01 ;+, Nick wrote:
> >One thing is that there don't appear to be any tags (at least with
> >surf, which is what I tested).
>
> Seems to work fine for me:
>
> >tony@morpheus ~ $ git clone git://git.suckless.org/surf
On 29/11/12 14:01 ;+, Nick wrote:
One thing is that there don't appear to be any tags (at least with
surf, which is what I tested).
Seems to work fine for me:
tony@morpheus ~ $ git clone git://git.suckless.org/surf
Cloning into 'surf'...
remote: Counting objects: 880, done.
remote: Compre
On Thu, Nov 29, 2012 at 04:09:35PM +0200, Daniel Bainton wrote:
> On 29 November 2012 16:01, Nick wrote:
> > Thanks Christoph, looks good. One thing is that there don't appear
> > to be any tags (at least with surf, which is what I tested). Can
> > these be migrated too? It'd be useful.
>
> You'r
On 29 November 2012 16:01, Nick wrote:
> (with apologies for screwing up threading slightly)
>
> Thanks Christoph, looks good. One thing is that there don't appear
> to be any tags (at least with surf, which is what I tested). Can
> these be migrated too? It'd be useful.
You're doing something wr
(with apologies for screwing up threading slightly)
Thanks Christoph, looks good. One thing is that there don't appear
to be any tags (at least with surf, which is what I tested). Can
these be migrated too? It'd be useful.
Nick
Greetings.
On Thu, 29 Nov 2012 14:48:17 +0100 uki wrote:
> there goes the 'less' part
> Pozdrawiam,
> Łukasz Gruner
You must have had a wrong definition of »suckless« long before this hap‐
pened, if you think using a prototyping language for many years without
replacing it »sucks less«.
Since
rofl
On 11/29/12, Roberto E. Vargas Caballero wrote:
>>Quick question -
>>A long time ago I asked if it was possible to clone _all_ the hg
>>repositories without having to manually specify them from the suckless
>>site. The answer I got was no.
>>With the transfer to git, woul
>Quick question -
>A long time ago I asked if it was possible to clone _all_ the hg
>repositories without having to manually specify them from the suckless
>site. The answer I got was no.
>With the transfer to git, would it be possible for me to clone all of the
>suckless re
there goes the 'less' part
Pozdrawiam,
Łukasz Gruner
2012/11/29 Christoph Lohmann <2...@r-36.net>:
> Greetings comrades,
>
> the migration to git is nearly complete. What’s missing is your tests
> that everything works as expected.
>
> Projects can be accessed via:
> http://git.suckles
25 matches
Mail list logo
