Commits
- Commit:
a4515c6608c1b685bfa9187b2517b44773a11068
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
got: drop commit -A $GOT_AUTHOR restriction
As discussed with op and stsp on irc, this prevents the valid case of
changing a commit's author to yourself during a histedit operation, and
potentially blocks other valid use cases too.
ok stsp@ and op@
- Commit:
1fa0d17d767f8e443af3b4493f3f2af0e759dda9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
got/tog/gotadmin: pledge earlier
In the case of tog move setlocale(3) before pledge(2), as suggested by
stsp.
ok stsp@
- Commit:
ff08dcd6c83d27f29c7eb78f7b21fee64bebfdd2
- From:
- Omar Polo <op@omarpolo.com>
- Date:
send_tree_entries: simplify len computing
- Commit:
f72ce919dd6d6c15679c5174c47912ac55be1e18
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Mark Jamsek <mark@jamsek.dev>
- Date:
make 'got fetch -b branch' error reporting more helpful
The patch to got-fetch-pack.c was written by stsp with only minor tweaks
by me. Regress updated to account for the change in reporting.
stsp's original got-fetch-pack.c diff ok op jamsek
ok stsp@
- Commit:
1cb79834eab33d1c1c01731b4800bab440032f20
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
regress: fetch -b/got.conf/wt/remote HEAD interaction
The added test checks we honour the correct precedence of branches to be
fetched, which is determined by: the -b flag; branches set in got.conf;
the work tree's current branch; and the remote repository's HEAD branch.
If a branch is specified with -b, only fetch this branch and if it does
not exist, simply report to the user--do not fallback to other branches.
Otherwise, if branches are either not set in got.conf or are set but do
not exist on the server:
- if invoked in a work tree, fallback to the work tree's current branch
- if not in a work tree or the work tree's current branch does not exist
on the server:
- fallback to remote HEAD.
With this, only the -b case can result in an unsuccessful fetch due to the
requested branch(es) not existing on the server. All other cases will either
fetch updates or report "Already up-to-date" (excepting errors).
ok stsp@
- Commit:
0dd7613ce65424868ec86f0623e38eb70d9a9321
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
special case 'got fetch -b <branch>' to only fetch <branch>
As discussed on irc, this drops the implicit remote HEAD fetch when -b is used.
got.1 has been updated to make the new fetch behaviour clear.
ok stsp@
- Commit:
7b771fb638e62245e029bcceaa32c0dce315b23c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
style
- Commit:
0c2ef172a69b83723fda636ca209754ac7995dc1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo
- Commit:
2c4740ad12b787db8704cb160abc4f1e5e73d911
- From:
- Mikhail <mp39590@gmail.com>
- Via:
- Mark Jamsek <mark@jamsek.dev>
- Date:
style(9): function call in initialiser patch by Mikhail
- Commit:
161b566ff8fdc61984f077c6ab1d75b5f0fd5ac7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
lib/object_create.c: calloc object ids
future fields added to the got_object_id will be implicitly zeroed
instead of gibberish.
ok stsp@
- Commit:
01392bd60410ca454e46653c8a740008e84545ef
- From:
- Tracey Emery <tracey@traceyemery.net>
- Date:
gotwebd: abort tree and blob as well
- Commit:
4f152e84c01e22799218a449a85a105ff94fdf9d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
gotwebd: abort blame if the client disconnect midway thru
Without setting err when the callback fails we continue the blame
machinery.
- Commit:
faf054c3d5fbad3a55534ebe525d58156c7aad27
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
make new log message modication check more robust; fixes regress fallout
ok jamsek
- Commit:
ccc835f12a86459f480a7ea4b724af67cd0889a7
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
garbage-collect redundant read_logmsg() parameter
As identified and suggested by stsp, with the previous commit,
'strip_comments' is now always set thus no longer needed.
ok stsp@
- Commit:
93436ccdaf0945f5fdb4b5cd2b90c9ac0bb14c83
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
got: use timestamp and emptiness to validate log message
As suggested by naddy: consider commit log messages valid provided the temp
file time stamp has changed and the file is not empty. This heuristic
provides the desired behaviour (i.e., reusing cherrypicked/backed-out log
messages) that's currently provided but is simpler to grok.
Improved by and ok stsp@