On Wed, Aug 24, 2016 at 05:27:31PM -0400, Jason A. Smith wrote:
> I will send a new updated patch that I think will fix most of the minor
> issues, but I am not exactly sure what you mean by the last note.
>
> On 08/24/2016 03:23 PM, John Keeping wrote:
> >> +int cgit_map_user(struct string_list
If a mailmap file is present in the repo, it will be used to coalesce
commits by the same person, just like git does. When no mailmap file is
found then it functions as before.
Signed-off-by: Jason A. Smith
---
cgit.h | 2 ++
parsing.c | 39 +++
ui-a
I will send a new updated patch that I think will fix most of the minor
issues, but I am not exactly sure what you mean by the last note.
On 08/24/2016 03:23 PM, John Keeping wrote:
+int cgit_map_user(struct string_list *map, char **email, char **name)
+{
+ char *map_email, *map_name;
+
On Wed, Aug 24, 2016 at 02:28:16PM -0400, Jason A. Smith wrote:
>
> If a mailmap file is present in the repo, it will be used to coalesce
> commits by the same person, just like git does. When no mailmap file is
> found then it functions as before.
Missing sign-off, see [1] for what this means.
On Wed, Aug 24, 2016 at 07:19:20AM +, Juuso Lapinlampi wrote:
> source-filter is good enough? I don't want cgit to become a GitLab-ish
> platform with all this featuritis.
source-filter doesn't suppress the line numbers, which render as a
separate table cell, and it wraps the content in . I'm
If a mailmap file is present in the repo, it will be used to coalesce
commits by the same person, just like git does. When no mailmap file is
found then it functions as before.
---
cgit.h | 3 +++
parsing.c | 43 +++
ui-atom.c | 9 +++--
ui-
On Wed, Aug 24, 2016 at 6:41 AM, Joe Anakata
wrote:
> On 08/23/2016 02:37 PM, Konstantin Ryabitsev wrote:
>> I tried using a source-filter to render markdown, but the results were not
>> quite there (see attachment). :) I don't think there's currently a way to do
>> it, but it would be pretty nice
source-filter is good enough? I don't want cgit to become a GitLab-ish
platform with all this featuritis.
Do one thing and do it well; leave Markdown rendering to a seperate
program. Nobody can really even agree to how Markdown and its quirks
should be rendered, so we have tens of variants. Common
