From: Lars Schneider <larsxschneider@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git Merge Contributor's Summit Mar 7, 2018, Barcelona
Date: Sat, 27 Jan 2018 14:36:10 +0100 [thread overview]
Message-ID: <F92D899E-C54B-4004-A957-FD167BD0E470@gmail.com> (raw)
In-Reply-To: <20180119001034.GA29172@sigill.intra.peff.net>
Hi Peff,
I would like to register to the contributor summit :-)
---
As I am writing you, I thought I could ask you a question:
"git verify-pack" tells me the "size-in-packfile" which is
kind of the "real" size of a file in a Git repo. Are you
aware of a way to get this number via the GitHub API?
We have written a GitHub bot (soon to be open sourced!) that
warns about large files. We query the file size via Repo Content
API [1]. Largish text files usually compress well and therefore
our bot generates false positive warnings.
I assume it is not possible to query "size-in-packfile" via GitHub
API as this is kind of an internal and not necessarily stable
number. But I thought maybe you happen to know some way!
Thanks,
Lars
[1] https://developer.github.com/v3/repos/contents/#get-content
PS: In my last email I asked you about AsciiDoc rendering via *.adoc
extension on GitHub. Your argument that Git has custom AsciiDoc
configs and attributes convinced me to not propose that idea on
the list.
> On 19 Jan 2018, at 01:10, Jeff King <peff@peff.net> wrote:
>
> Git Merge 2018 is happening on March 8th; there will be a Contributor's
> Summit the day before. Here are the details:
>
> When: Wednesday, March 7, 2018. 10am-5pm.
> Where: Convent Dels Àngels[1], Barcelona, Spain
> What: Round-table discussion about Git
> Who: All contributors to Git or related projects in the Git ecosystem
> are invited; if you're not sure if you qualify, just ask!
>
> In order to attend, you'll need to register ahead of time. There's a
> super-secret link to do so; email me and I will provide it.
> Registration is free, and comes with a ticket to the main conference on
> the 8th (which I encourage you to attend, but you don't have to).
>
> As with past years, the agenda is whatever we choose. We'll have room
> for about 25 people with "boardroom-style seating" and a projector.
> Come prepared with topics to present or discuss.
>
> If you're interested in financial aid for traveling to the conference,
> please send an email to git@sfconservancy.org. And please do so soon
> (let's say by the end of next week, Jan 26th), so that we have an idea
> of the number and size of requests before making any grants.
>
> -Peff
>
> [1] https://www.google.com/maps/place/Convent+Dels+Angels/@41.3827189,2.1652982,17z/data=!3m1!4b1!4m5!3m4!1s0x12a4a310123f3dc1:0x4588a81b66dce9dc!8m2!3d41.3827189!4d2.1674869
prev parent reply other threads:[~2018-01-27 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 0:10 [ANNOUNCE] Git Merge Contributor's Summit Mar 7, 2018, Barcelona Jeff King
2018-01-27 13:36 ` Lars Schneider [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F92D899E-C54B-4004-A957-FD167BD0E470@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).