List for cgit developers and users
 help / color / mirror / Atom feed
From: list at eworm.de (Christian Hesse)
Subject: Release plan for 1.2
Date: Wed, 25 Jul 2018 12:06:27 +0200	[thread overview]
Message-ID: <20180725120627.5fdb32f1@leda> (raw)
In-Reply-To: <20180713201246.GA17028@chatter>

Konstantin Ryabitsev <konstantin at linuxfoundation.org> on Fri, 2018/07/13
16:12:
> On Wed, Jul 04, 2018 at 03:23:22AM +0200, Jason A. Donenfeld wrote:
> >Either way, kernel.org's Konstantin is back next week, at which time I
> >expect he'll give the new archive signature notes feature a spin, and
> >if it works as intended, I think I'll release shortly after. Between
> >now and then, that leaves us some time for refining things as they
> >come up.  
> 
> Jason:
> 
> The .tar signatures are looking good to me, thanks so much for getting 
> that in! You can see them in action (using my test repo, for now):
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/hook-test.git/
> 
> I'll start the work switching things over to this new hotness once the 
> official 1.2 is out.

I found the first signature in the wild:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tag/?h=v4.4.144

Who is supposed to push these signatures? Will the developers have to or is
there any automatism to sync static archives and git notes?
-- 
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/20180725/56e57669/attachment.asc>


  parent reply	other threads:[~2018-07-25 10:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  1:23 Jason
2018-07-04  4:56 ` dlcampbell
2018-07-04  5:58 ` list
2018-07-13 20:12 ` konstantin
2018-07-13 20:32   ` Jason
2018-07-13 20:43   ` list
2018-07-13 21:01     ` konstantin
2018-07-25 10:06   ` list [this message]
2018-07-25 13:15     ` konstantin

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=20180725120627.5fdb32f1@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).