Christian Hesse on Thu, 2018/06/14 00:52:
> Update to git version v2.18.0-rc2. Required changes follow upstream commits:
I've pushed John's snapshot series to ch/for-jason. Does anybody agree that
we want that? I will rebase the final commit on ch/for-jason then.
--
main(a){char*c=/*Schoene
John Keeping on Sat, 2018/06/16 17:14:
> With Andy's fix,
>
> Reviewed-by: John Keeping
That is in git 2.17.1 commit already. ;)
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Best regards my address:*/=0;b=c[a++];)
On Sat, Jun 16, 2018 at 6:14 PM John Keeping wrote:
> But we still have a few mentions of sha1 in our code. Most of this is
> sha1 and sha2 in struct cgit_query, but these aren't actually hashes
> most of the time, they can be any object reference that Git understands,
> so I think we should
On Thu, Jun 14, 2018 at 12:52:25AM +0200, Christian Hesse wrote:
> From: Christian Hesse
>
> Update to git version v2.18.0-rc2. Required changes follow upstream commits:
>
> * Convert find_unique_abbrev* to struct object_id
> (aab9583f7b5ea5463eb3f653a0b4ecac7539dc94)
> * sha1_file: convert
From: Christian Hesse
Update to git version v2.18.0-rc2. Required changes follow upstream commits:
* Convert find_unique_abbrev* to struct object_id
(aab9583f7b5ea5463eb3f653a0b4ecac7539dc94)
* sha1_file: convert read_sha1_file to struct object_id
(b4f5aca40e6f77cbabcbf4ff003c3cf30a1830c8)
