summary refs log tree commit diff
path: root/gfx
diff options
context:
space:
mode:
authorJune McEnroe <programble@gmail.com>2017-11-04 22:29:32 -0400
committerJune McEnroe <programble@gmail.com>2018-04-03 22:01:05 -0400
commit706eda90d688eeace7d5e588b6e60336bc4d373f (patch)
tree86456e78be86baf299032f619823dc43436df414 /gfx
parentAdd MASSEDUCTION (diff)
downloadsrc-706eda90d688eeace7d5e588b6e60336bc4d373f.tar.gz
src-706eda90d688eeace7d5e588b6e60336bc4d373f.zip
Add The Dusk in Us
Diffstat (limited to 'gfx')
0 files changed, 0 insertions, 0 deletions
 

generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-11-05 14:56:50 +0000


 


48a64aea78907878c&follow=1'>Allow removing bodies and lensesJune McEnroe
2024-09-08Limit body width so it looks less silly on desktopJune McEnroe
2024-09-07Handle no film being loadedJune McEnroe
2024-09-07Fancy up the text a littleJune McEnroe2019-12-20 18:26:15 -0500'>2019-12-20Set LANG in cgit filtersJune McEnroe
2019-12-20Source .editrc before applying -v or -eJune McEnroe
2019-12-20Disable signing commitsJune McEnroe
2019-12-19Ignore about-filterJune McEnroe
2019-12-19Fix matching make tags with no sourcesJune McEnroe
2019-12-19Avoid matching := assignments as tagsJune McEnroe
2019-12-18Hide line numbers when rendering mdocJune McEnroe
2019-12-18Customize cgit CSSJune McEnroe
2019-12-18Use :target rather than :focus pseudo-classJune McEnroe
2019-12-18Copy cgit auxiliary binaries properlyJune McEnroe
2019-12-18Add git.causal.agency cgit configJune McEnroe
2019-12-18Bail from hi if input is binaryJune McEnroe
2019-12-16Post "cgit setup"June McEnroe30f62c8f061062bc4a9ba962b6910&follow=1'>Makefile: include Git's config.mak.unameJohn Keeping

This pulls in the correct value of $(INSTALL) on a wide variety of
systems.

Signed-off-by: John Keeping <john@keeping.me.uk>



2015-08-13tests: allow shell to be overriddenJohn Keeping

On some systems (e.g. Solaris), /bin/sh is not a POSIX shell.  Git
already provides suitable overrides in its config.mak.uname file and we
provide cgit.conf to allow the user to further change this.

The code for this is taken from Git's t/Makefile, meaning that we now
invoke the tests in the same way that Git does.

Signed-off-by: John Keeping <john@keeping.me.uk>



2015-08-13redirect: cleanlinessJason A. Donenfeld


2015-08-13redirect: be more careful for different cgi setupsJason A. Donenfeld


2015-08-12ui-log: fix double countingJohn Keeping

This crept in while rebasing the previous commit onto an updated
upstream.

Signed-off-by: John Keeping <john@keeping.me.uk>



2015-08-12log: allow users to follow a fileJohn Keeping

Teach the "log" UI to behave in the same way as "git log --follow", when
given a suitable instruction by the user.  The default behaviour remains
to show the log without following renames, but the follow behaviour can
be activated by following a link in the page header.

Follow is not the default because outputting merges in follow mode is
tricky ("git log --follow" will not show merges).  We also disable the
graph in follow mode because the commit graph is not simplified so we
end up with frequent gaps in the graph and many lines that do not
connect with any commits we're actually showing.

We also teach the "diff" and "commit" UIs to respect the follow flag on
URLs, causing the single-file version of these UIs to detect renames.
This feature is needed only for commits that rename the path we're
interested in.

For commits before the file has been renamed (i.e. that appear later in
the log list) we change the file path in the links from the log to point
to the old name; this means that links to commits always limit by the
path known to that commit.  If we didn't do this we would need to walk
down the log diff'ing every commit whenever we want to show a commit.
The drawback is that the "Log" link in the top bar of such a page links
to the log limited by the old name, so it will only show pre-rename
commits.  I consider this a reasonable trade-off since the "Back" button
still works and the log matches the path displayed in the top bar.

Since following renames requires running diff on every commit we
consider, I've added a knob to the configuration file to globally
enable/disable this feature.  Note that we may consider a large number
of commits the revision walking machinery no longer performs any path
limitation so we have to examine every commit until we find a page full
of commits that affect the target path or something related to it.

Suggested-by: René Neumann <necoro@necoro.eu>
Signed-off-by: John Keeping <john@keeping.me.uk>



2015-08-12shared: make cgit_diff_tree_cb publicJohn Keeping

This will allow us to use this nice wrapper function elsewhere, avoiding
dealing with the diff queue when we only need to inspect a filepair.

Signed-off-by: John Keeping <john@keeping.me.uk>



2015-08-12t0110: Chain together using &&Jason A. Donenfeld


2015-08-12about: always ensure page has a trailing slashJason A. Donenfeld

Otherwise we can't easily embed links to other /about/ pages.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>



2015-08-12filters: apply HTML escapingLazaros Koromilas

http://www.w3.org/International/questions/qa-escapes#use



2015-08-12git: update to v2.5.0Christian Hesse

Update to git version v2.5.0.

* Upstream commit 5455ee0573a22bb793a7083d593ae1ace909cd4c (Merge branch
  'bc/object-id') changed API:

  for_each_ref() callback functions were taught to name the objects
  not with "unsigned char sha1[20]" but with "struct object_id".

* Upstream commit dcf692625ac569fefbe52269061230f4fde10e47 (path.c: make
  get_pathname() call sites return const char *)

Signed-off-by: Christian Hesse <mail@eworm.de>



2015-08-12Fix processing of repo.hide and repo.ignoreDaniel Reichelt