From: Tobias.Bieniek at gmx.de (Tobias Bieniek)
Subject: Maintaining My Own Cgit Tree
Date: Thu, 27 Sep 2012 11:00:53 +0200 [thread overview]
Message-ID: <CABEOeTnakb86KuDmxhROXXJ-gS_QKHcMAwqw78Cn0FE+X-xu+g@mail.gmail.com> (raw)
In-Reply-To: <5063D48E.3000301@frog.za.net>
Thanks Jason. I think that is a good idea. Too bad that Lars did not
leave any information... I've forwarded my three small patches too you
and hope that you will find them useful.
Turbo
2012/9/27 William Bell <william.bell at frog.za.net>:
> Wonderful
>
>
>
> On 27/09/2012 03:39, Jason A. Donenfeld wrote:
>>
>> Hi everyone,
>>
>> I haven't heard from Lars for almost 7 months now. I've contributed
>> chunks of code to cgit in the past, and I continue to improve it now,
>> but with no one to send patches to, I've just been maintaining my own
>> tree, with features such as better support for the latest gitolite,
>> among other fixes.
>>
>> Until Lars appears on the scene again, I'm happy to aggregate a
>> patches from everyone in my tree, and then when he reemerges from
>> wherever he is, he'll have a nice unified place to start merging what
>> we've been up to during his absence.
>>
>> If others like this plan, by all means resend to this thread the
>> patches and enhancements you've been working on.
>>
>> You can see what I've added myself at: http://git.zx2c4.com/cgit
>>
>> Thanks,
>> Jason Donenfeld
>>
>> _______________________________________________
>> cgit mailing list
>> cgit at hjemli.net
>> http://hjemli.net/mailman/listinfo/cgit
>>
>
> _______________________________________________
> cgit mailing list
> cgit at hjemli.net
> http://hjemli.net/mailman/listinfo/cgit
next prev parent reply other threads:[~2012-09-27 9:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 1:39 Jason
2012-09-27 4:22 ` william.bell
2012-09-27 9:00 ` Tobias.Bieniek [this message]
2012-09-27 15:53 ` webmaster
2012-09-29 0:30 ` [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
2012-09-29 5:20 ` Jason
2012-09-29 18:43 ` lsworkemail112
2012-09-29 18:51 ` Jason
2012-09-29 19:14 ` lsworkemail112
2012-09-29 19:15 ` Jason
2012-09-29 19:17 ` lsworkemail112
2012-09-29 19:16 ` lsworkemail112
2012-09-30 5:51 ` mailings
2012-09-30 17:28 ` lsworkemail112
2012-09-30 17:29 ` Jason
2012-09-30 17:40 ` mailings
2012-09-30 21:06 ` lsworkemail112
2012-09-30 21:33 ` Jason
2012-10-01 6:12 ` mailings
2012-10-02 1:46 ` lsworkemail112
2012-10-02 2:04 ` Jason
2012-10-02 2:08 ` lsworkemail112
2012-10-01 13:56 ` webmaster
2012-10-08 16:48 ` [PATCH 1/2] add git config parsing during scan-path jamie.couture
2012-10-08 16:48 ` [PATCH 2/2] update documentation jamie.couture
2012-10-08 21:05 `
2012-10-08 21:18 `
2012-10-08 16:49 ` [PATCH] repolist pagination changes jamie.couture
2012-10-08 21:39 ` Jason
2012-10-08 17:12 ` [PATCH] add tag target to generate ctags jamie.couture
2012-10-08 21:41 ` Jason
2012-10-09 10:56 ` [PATCH] add git config parsing during scan-path jamie.couture
2012-10-09 11:33 ` Jason
2012-10-09 11:15 ` Maintaining My Own Cgit Tree mailings
2012-10-09 11:18 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABEOeTnakb86KuDmxhROXXJ-gS_QKHcMAwqw78Cn0FE+X-xu+g@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).