summary refs log tree commit diff
path: root/bin/1sh
diff options
context:
space:
mode:
authorJune McEnroe <june@causal.agency>2018-09-17 22:54:38 -0400
committerJune McEnroe <june@causal.agency>2018-09-17 22:54:38 -0400
commit8db02d728d96b8900aa17e80b90793e2f1b5fd30 (patch)
treec8443c89cf3e3d84165d247062f5a498f75bbe89 /bin/1sh
parentMake install target depend on text files (diff)
downloadsrc-8db02d728d96b8900aa17e80b90793e2f1b5fd30.tar.gz
src-8db02d728d96b8900aa17e80b90793e2f1b5fd30.zip
Use install(1) to install
Diffstat (limited to 'bin/1sh')
0 files changed, 0 insertions, 0 deletions
 

generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-14 18:20:22 +0000


 


eaders in only one place.

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



2015-08-13cache.c: fix header orderJohn Keeping

git-compat-util.h may define values that affect how system headers are
interpreted, so move sys/sendfile.h after cgit.h (which includes
git-compat-util.h).

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



2015-08-13configfile.c: don't include system headers directlyJohn Keeping

git-compat-util.h may define various values that affect the
interpretation of system headers.  In most places we include cgit.h
first, which pulls in git-compat-util.h, but this file does not depend
on anything else in CGit, so use git-compat-util.h directly.

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



2015-08-13Remove redundant includesJohn Keeping

These are all included in git-compat-util.h (when necessary), which we
include in cgit.h.

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



2015-08-13Makefile: 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