List for cgit developers and users
 help / color / mirror / Atom feed
From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] RFC: git: update to v2.19.0-rc0
Date: Tue, 21 Aug 2018 11:02:56 +0200	[thread overview]
Message-ID: <20180821110256.049ffe95@leda> (raw)
In-Reply-To: <20180821084650.GD2084@john.keeping.me.uk>

John Keeping <john at keeping.me.uk> on Tue, 2018/08/21 09:46:
> On Tue, Aug 21, 2018 at 09:21:14AM +0200, Christian Hesse wrote:
> > From: Christian Hesse <mail at eworm.de>
> > 
> > Changelog to be writting... :)  
> 
> More comments below, but it looks like there's a lot of unrelated
> cleanups here.  I think only the the_repository parameter addition is
> required for Git 2.19.
> 
> The other changes mostly look good, but I think they can be split out
> into a separate series (which can probably land before Git 2.19 final is
> released).

This is related to git 2.19, see "Merge branch 'jk/banned-function'" [0].
But you are right this can go in in separate patches if we do it before
git 2.19 final.

I will look at your comments. Thanks!

[0] https://github.com/git/git/commit/e28daf222f51f137d9038a58812f2a89f414781e
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180821/7f5db86d/attachment-0001.asc>


  reply	other threads:[~2018-08-21  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21  7:21 list
2018-08-21  8:46 ` john
2018-08-21  9:02   ` list [this message]
2018-08-28 16:06   ` list

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180821110256.049ffe95@leda \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).