Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Mon, Aug 08, 2016 at 08:48:55AM +0200, Torsten Bögershausen wrote: > On 2016-08-05 01.32, Junio C Hamano wrote: > > Mike Hommey writes: > [] > > >> What kind of support are you expecting? > > > > The only rationale I recall you justifying this series was that this > >

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On 2016-08-05 01.32, Junio C Hamano wrote: > Mike Hommey writes: [] >> What kind of support are you expecting? > > The only rationale I recall you justifying this series was that this > makes the resulting code easier to read, but I do not recall other > people agreeing with

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Hi Junio, On Thu, 4 Aug 2016, Junio C Hamano wrote: > * js/import-tars-hardlinks (2016-08-03) 1 commit > - import-tars: support hard links > > "import-tars" fast-import script (in contrib/) used to ignore a > hardlink target and replaced it with an empty file, which has been > corrected to

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Jeff King wrote: > On Fri, Aug 05, 2016 at 08:26:30AM +, Eric Wong wrote: > > > > I'm not sure which mallocs you mean. I allocate one struct per node, > > > which seems like a requirement for a linked list. If you mean holding an > > > extra list struct around an existing

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Fri, Aug 05, 2016 at 08:26:30AM +, Eric Wong wrote: > > I'm not sure which mallocs you mean. I allocate one struct per node, > > which seems like a requirement for a linked list. If you mean holding an > > extra list struct around an existing pointer (rather than shoving the > > prev/next

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Jeff King wrote: > On Fri, Aug 05, 2016 at 08:02:31AM +, Eric Wong wrote: > > > > I just introduced another doubly-linked list in [1]. It adds some MRU > > > features on top of the list, but it could in theory be built on top of a > > > generic doubly-linked list. > > > >

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Fri, Aug 05, 2016 at 08:02:31AM +, Eric Wong wrote: > > I just introduced another doubly-linked list in [1]. It adds some MRU > > features on top of the list, but it could in theory be built on top of a > > generic doubly-linked list. > > Yes, and you'd be avoiding the extra mallocs and

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

(Fixed Nico's address) Jeff King wrote: > On Thu, Aug 04, 2016 at 11:34:35PM +, Eric Wong wrote: > > Junio C Hamano wrote: > > > [Graduated to "master"] > > > > > * ew/http-walker (2016-07-18) 4 commits > > > (merged to 'next' on 2016-07-18 at a430a97) >

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Thu, Aug 04, 2016 at 11:34:35PM +, Eric Wong wrote: > Junio C Hamano wrote: > > [Graduated to "master"] > > > * ew/http-walker (2016-07-18) 4 commits > > (merged to 'next' on 2016-07-18 at a430a97) > > + list: avoid incompatibility with *BSD sys/queue.h > >

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Eric Wong writes: > Yay! This finally introduces the Linux kernel linked list > into git. I'm not sure if it's worth the effort to introduce > cleanup commits to start using it in places where we already > have doubly-linked list implementations: > > (+Cc Nicolas and Lukas) > *

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Thu, Aug 04, 2016 at 04:32:02PM -0700, Junio C Hamano wrote: > Mike Hommey writes: > > > On Thu, Aug 04, 2016 at 03:28:55PM -0700, Junio C Hamano wrote: > >> * mh/connect (2016-06-06) 10 commits > >> - connect: [host:port] is legacy for ssh > >> ... > >> - connect:

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Junio C Hamano wrote: > [Graduated to "master"] > * ew/http-walker (2016-07-18) 4 commits > (merged to 'next' on 2016-07-18 at a430a97) > + list: avoid incompatibility with *BSD sys/queue.h > (merged to 'next' on 2016-07-13 at 8585c03) > + http-walker: reduce O(n) ops

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

"Philip Oakley" writes: >> Updates in 4/8 ("give headings") is reported to break formatting? >> cf. <57913c97.1030...@xiplink.com> > > Just to say I haven't forgotten. OK. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

Mike Hommey writes: > On Thu, Aug 04, 2016 at 03:28:55PM -0700, Junio C Hamano wrote: >> * mh/connect (2016-06-06) 10 commits >> - connect: [host:port] is legacy for ssh >> ... >> - connect: document why we sometimes call get_port after get_host_and_port >> >> Rewrite

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

From: "Junio C Hamano" * po/range-doc (2016-07-20) 8 commits - doc: revisions - clarify reachability examples - doc: revisions - define `reachable` - doc: gitrevisions - clarify 'latter case' is revision walk - doc: gitrevisions - use 'reachable' in page description - doc:

Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)

On Thu, Aug 04, 2016 at 03:28:55PM -0700, Junio C Hamano wrote: > * mh/connect (2016-06-06) 10 commits > - connect: [host:port] is legacy for ssh > - connect: move ssh command line preparation to a separate function > - connect: actively reject git:// urls with a user part > - connect: change

What's cooking in git.git (Aug 2016, #02; Thu, 4)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. Many topics in "Cooking" section