As i have my cgit + uwsgi + nginx + gitolite setup in a LXD container, i
can publish it.
Would this be helpful?
Am 18.02.2017 um 17:57 schrieb John Keeping:
> On Tue, Jan 24, 2017 at 11:19:09PM +0100, MonkZ wrote:
>> i'm using cgit 1.1 and trying to configure a global list of possible
>> readme
Thanks. I'll review and merge.
___
CGit mailing list
CGit@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/cgit
Seems most reasonable to simply keep it something static and not add a nob.
However, John - you raise a good point. Git's diff feature isn't
exactly stable itself, with all sorts of interesting new diffing
strategies being tried out in newer versions. So perhaps this isn't
really an feasible goal
On Sun, Dec 04, 2016 at 08:45:04AM +, ilove zfs wrote:
> I'm reporting this as a result of this issue
> https://github.com/Homebrew/homebrew-core/issues/5353 which was filed
> with Homebrew regarding cgit.
>
> The cgit patch links do not have stable checksums because of the cgit
> version
Hi Jason,
[Apologies for sending this twice, I forgot to add the list on the first
attempt.]
The following changes since commit be39d22328f841536b8e44e8aaeed80a74ebb353:
ui-patch: fix crash when using path limit (2017-01-23 18:36:04 +0100)
are available in the git repository at:
On Tue, Jan 24, 2017 at 11:19:09PM +0100, MonkZ wrote:
> i'm using cgit 1.1 and trying to configure a global list of possible
> readme files (see attachment), but all i can get to work are
> "cgit.readme" entries in git-config files.
>
> I would expect, that this list would be active until a repo
On Fri, Feb 03, 2017 at 08:06:06PM -0800, Bertrand Roussel wrote:
> Add option 'show-all-refs' and 'repo.show-all-refs' to display references
> that are not tags or branches.
Missing Signed-off-by tag (see [0]).
Other than that, I wonder why this doesn't touch ui-refs.c or
ui-summary.c. If this
On Tue, Dec 06, 2016 at 06:58:04PM +0100, Petr Vorel wrote:
> Teach cgit split the repository link in the top of repository "summary"
> view. This emulates the same behaviour as it's in gitweb.
>
> This behaviour is not implemented for repositories which have
> "repo.name" set different than
