[feature request] git-daemon http connection filtering of client types

Hey folks, When I checked for false positives in my spam this morning, I spotted an interesting malformed img link at the top of a spam message. {snip} > > > Employ a medal tiffany bracelet <{snip}> a is {snip} So, apparently git-daemon's htt

Re: [PATCH 4/6] introduce a commit metapack

On Wed, Jan 30, 2013 at 09:16:29PM +0700, Duy Nguyen wrote: > Perhaps we could store abbrev sha-1 instead of full sha-1. Nice > space/time trade-off. Following the on-disk format experiment yesterday, I changed the format to: - a list a _short_ SHA-1 of cached commits - a list of cache entries,

Re: How to identify the users?

On 01/31/2013 12:23 PM, Scott Yan wrote: > Sitaram: > > It seems I must host my central repo on Gitolite first... There is no "must" but yes it is a decent solution and can, in principle, do the kind of checking you want if you set it up to do that. Please note that I don't use that mode and, a

Re: Segmentation fault with latest git (070c57df)

On Thu, Jan 31, 2013 at 09:42:07AM +0100, Thomas Rast wrote: > > int main(void) > > { > > struct foo f = { NULL, 0, 0, 0 }; > > printf("cmp is %lu\n", (unsigned long)f.cmp); > > return 0; > > } > > I doubt that would help because that stack region would be 0 anyway due > to kernel initializ

Re: Segmentation fault with latest git (070c57df)

Jeff King writes: > On Thu, Jan 31, 2013 at 07:27:04AM +, Jongman Heo wrote: > >> FYI, gdb backtrace and valgrind output attached below, Thanks. > > Thanks, that's helpful. > >> #4 0x0812bda0 in string_list_insert (list=0xbfffe7c0, >> string=0x821ec3c "refs/remotes/origin/HEAD") at string-lis

Re: Re: Re: Segmentation fault with latest git (070c57df)

> It's almost like the compiler is getting the initializer wrong. It's a > long shot, but I wonder if the presence of the bitfield could be > triggering a compiler bug (or there is a subtle C rule about bitfield > initializations that I do not know). Just for the sake of my sanity, > what does the

<    1   2