rather than the list below.*

Consider [a sample email

which shows how a developer proposed a change and a patch to implement

it. The problem being solved, the design of the proposed solution,

and the implementation of that design were all reviewed and discussed,

In addition to what we discussed, I think files named by include.path

never the other way around", it is handy to be able to first find

a merge on the trunk that merged a topic to point fingers at when

a bug appears, instead of having to drill down to the individual

A patch for this feature was sent to the mailing list in this thread a

few years ago by Dscho:

Unfortunately there were some problems with the patch and no one tried

to fix them. So the same problem/suggestion is often reported on the

mailing list, for example:

A patch series to let "old/new" be used instead of "good/bad" was

started here:

There is still work to be done to complete it.

Note than another feature with the name "git bisect fix" was suggested

to do something else:

Since there have already been discussions and patches, the remaining

work is probably less than a GSoC, so this project should be grouped

"git config", when removing the last variable in a section, leaves an

empty section header behind. Anybody who wants to improve this needs

to consider ramifications of leaving or removing comments.

Takes eol attributes into account to correct lossage/addition of CR at

is 'fast'. Instead of failing, it could offer the user to reverse the

terms and continue the bisection.

The change is controversial, hence a substantial part of the project

would be to define what is the right behavior (should it be activated

"git config", when removing the last variable in a section, leaves an

empty section header behind. Anybody who wants to improve this needs

to consider ramifications of leaving or removing comments.

are the potential dangers, ... Reaching a solution that effectively

protects beginners without harming anyone is much harder than it

seems. See for example [this

for example potential objections. If chosen, this project should be

discussed in depth on the list before and after the student

application.

Following up to a message from David Kastrup, a discussion was initiated

by Christian Couder where Michael J Gruber noted

Paul Tan, who will probably apply to be a [Google Summer of Code

(GSoC)](https://developers.google.com/open-source/soc/) student for

Dongcan Jiang, who will also probably apply to be a GSoC student for

Git this year, sent a patch to prevent `git log` from being used with both

We often see review comments on test scripts that points out a

breakage in the &&-chain, but what does that mean?

People often ask the Git mailing list whether they can use Git to manage

special content. Fortunately, the list is monitored by many experts in different

Jeff King, alias Peff, posted a patch series to address speed

regressions when accessing the packed-refs file. This lead to

[gitforteams GitHub repo](https://github.com/emmajane/gitforteams), and also in an

[upcoming Git for Teams of One or More book](http://gitforteams.com/books/).

At the Contributor Summit that was part of the [Git Merge 2015](http://git-merge.com),

Jeff King, aka Peff, gave a presentation about the status of Git as a

[Software Freedom Conservancy (SFC)](https://sfconservancy.org/) project.

This gives some legal status to "The Git Project" and makes it possible for it

to handle money (around $19,000), hold domain names (git-scm.com, git-scm.org) and

[the "Git" trademark](https://git-scm.com/trademark), and own a Mac!

Karthik Nayak, a Google Summer of Code student, has been working for

some months on developing the `--allow-unknown-type` option for `git cat-file`.

He has been helped by Eric Sunshine, Ramsay Jones, Phil Hord, Charles Bailey, David Turner, Duy Nguyen,

Jeff King and Junio Hamano, and, along the development, improving the test script led

in `hash-object --literally`.

The 10th iteration of his patch series was merged to the 'next' branch,

so the new option will probably appear in the next git release.

Sébastien Guimmara started working on improving the output of `git help`.

In the case of Sébastien's patch series, many developers helped or got

involved in the discussions: Eric Sunshine, Junio Hamano, Stefan

Beller, Matthieu Moy, Johannes Schindelin, Johannes Sixt. Emma Jane Hogbin Westby

with her experience in teaching Git to people, which is a valuable

piece of input.

Phillip Susi had trouble getting gitk to show notes. Michael J. Gruber

tried to help him, but it didn't work when adding a note while gitk is

asked if `git notes list` is the best way to find out all the current

notes, and Johan Herland who developed `git notes` answered yes.

Joey Hess who is developing [git-annex](https://git-annex.branchable.com/) was surprised by how

`git ls-files` expands wildcard characters like `*[]` and the fact that escaping these characters

it is a good idea to use them in script or tools, like GitHub is doing

on their servers.

Eduardo Espejo found that Git does not compile anymore when using the

`NO_IPV6` configuration switch. And it is not the first time that

This time Junio Hamano, the Git maintainer, fixed the breakage in

"daemon.c", but more importantly found that `NO_CURL` and `NO_EXPAT`

configurations did not to pass the test suite.

And now he has a nightly cron job to try building

and testing a few selected configurations.

For a long time Git has been participating in [the Google Summer of Code](http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/about_page).

This summer two students, Paul Tan and Karthik Nayak, mentored by four experienced Git developers, Johannes Schindelin, Stefan Beller, Matthieu Moy and Christian Couder, will work on improving Git and will receive a stipend from Google.