Re: What's cooking in git.git (Jul 2016, #04; Mon, 11)

[Johannes Schindelin]

Hi Junio,

On Tue, 12 Jul 2016, Junio C Hamano wrote:

> On Tue, Jul 12, 2016 at 6:16 AM, Johannes Schindelin
>  wrote:
> >
> > On Mon, 11 Jul 2016, Junio C Hamano wrote:
> >
> >> [New Topics]
> >>
> >> [...]
> >
> > What about http://thread.gmane.org/gmane.comp.version-control.git/299050?
> 
> Not forgotten.
> 
> It just is not one of the "New Topics" yet, together with several
> other patches sent to
> the list recently, hence it is not listed there.

Thanks.

I just nudged you because this is a patch I needed to include it in Git
for Windows and would have loved more reviews than just mine.

Not a big deal, especially because it is not forgotten ;-)

Ciao,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: What's cooking in git.git (Jul 2016, #04; Mon, 11)

[Junio C Hamano]

On Tue, Jul 12, 2016 at 6:16 AM, Johannes Schindelin
 wrote:
>
> On Mon, 11 Jul 2016, Junio C Hamano wrote:
>
>> [New Topics]
>>
>> [...]
>
> What about http://thread.gmane.org/gmane.comp.version-control.git/299050?

Not forgotten.

It just is not one of the "New Topics" yet, together with several
other patches sent to
the list recently, hence it is not listed there.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: What's cooking in git.git (Jul 2016, #04; Mon, 11)

[Johannes Schindelin]

Hi Junio,

On Mon, 11 Jul 2016, Junio C Hamano wrote:

> [New Topics]
> 
> [...]

What about http://thread.gmane.org/gmane.comp.version-control.git/299050?

Ciao,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

What's cooking in git.git (Jul 2016, #04; Mon, 11)

[Junio C Hamano]

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.

The first maintenance release for 2.9.x series has been issued.

You can find the changes described here in the integration branches
of the repositories listed at

http://git-blame.blogspot.com/p/git-public-repositories.html

--
[Graduated to "master"]

* jc/send-email-skip-backup (2016-04-12) 1 commit
  (merged to 'next' on 2016-06-28 at 67dac59)
 + send-email: detect and offer to skip backup files

 A careless invocation of "git send-email directory/" after editing
 0001-change.patch with an editor often ends up sending both
 0001-change.patch and its backup file, 0001-change.patch~, causing
 embarrassment and a minor confusion.  Detect such an input and
 offer to skip the backup files when sending the patches out.
 Perhaps people will enhance it more once it gains more visibility.


* jk/ansi-color (2016-06-23) 7 commits
  (merged to 'next' on 2016-06-28 at 354989c)
 + color: support strike-through attribute
 + color: support "italic" attribute
 + color: allow "no-" for negating attributes
 + color: refactor parse_attr
 + add skip_prefix_mem helper
 + doc: refactor description of color format
 + color: fix max-size comment

 The output coloring scheme learned two new attributes, italic and
 strike, in addition to existing bold, reverse, etc.


* jk/perf-any-version (2016-06-22) 2 commits
  (merged to 'next' on 2016-06-28 at 6a41c30)
 + p4211: explicitly disable renames in no-rename test
 + t/perf: fix regression in testing older versions of git

 Allow t/perf framework to use the features from the most recent
 version of Git even when testing an older installed version.


* jn/preformatted-doc-url (2016-06-22) 1 commit
  (merged to 'next' on 2016-06-28 at 60a99eb)
 + doc: git-htmldocs.googlecode.com is no more

 The top level documentation "git help git" still pointed at the
 documentation set hosted at now-defunct google-code repository.
 Update it to point to https://git.github.io/htmldocs/git.html
 instead.


* js/color-on-windows-comment (2016-06-28) 1 commit
  (merged to 'next' on 2016-06-28 at 38a2ea1)
 + color.h: remove obsolete comment about limitations on Windows

 For a long time, we carried an in-code comment that said our
 colored output would work only when we use fprintf/fputs on
 Windows, which no longer is the case for the past few years.


* js/find-commit-subject-ignore-leading-blanks (2016-06-29) 5 commits
  (merged to 'next' on 2016-06-29 at 9717e00)
 + reset --hard: skip blank lines when reporting the commit subject
 + sequencer: use skip_blank_lines() to find the commit subject
 + commit -C: skip blank lines at the beginning of the message
  (merged to 'next' on 2016-06-28 at 32bbd94)
 + commit.c: make find_commit_subject() more robust
 + pretty: make the skip_blank_lines() function public

 A helper function that takes the contents of a commit object and
 finds its subject line did not ignore leading blank lines, as is
 commonly done by other codepaths.  Make it ignore leading blank
 lines to match.


* mj/log-show-signature-conf (2016-06-24) 3 commits
  (merged to 'next' on 2016-06-28 at c8b3347)
 + log: add log.showSignature configuration variable
 + log: add "--no-show-signature" command line option
 + t4202: refactor test

 "git log" learns log.showSignature configuration variable, and a
 command line option "--no-show-signature" to countermand it.


* sb/submodule-clone-retry (2016-06-13) 2 commits
  (merged to 'next' on 2016-06-28 at 8a86d54)
 + submodule update: continue when a clone fails
 + submodule--helper: initial clone learns retry logic

 "git submodule update" that drives many "git clone" could
 eventually hit flaky servers/network conditions on one of the
 submodules; the command learned to retry the attempt.

--
[New Topics]

* js/ignore-space-at-eol (2016-07-11) 2 commits
 - diff: fix a double off-by-one with --ignore-space-at-eol
 - diff: demonstrate a bug with --patience and --ignore-space-at-eol

 An age old bug that caused "git diff --ignore-space-at-eol"
 misbehave has been fixed.

 Will merge to 'next'.


* js/rebase-i-tests (2016-07-07) 3 commits
 - rebase -i: we allow extra spaces after fixup!/squash!
 - rebase -i: demonstrate a bug with --autosquash
 - t3404: add a test for the --gpg-sign option

 A few tests that specifically target "git rebase -i" have been
 added.

 Will merge to 'next'.


--
[Stalled]

* jh/clean-smudge-annex (2016-07-08) 9 commits
 - SQUASH??? compilation fix
 - use smudgeToFile filter in recursive merge
 - use smudgeToFile filter in git am
 - better recovery from failure of smudgeToFile filter
 - warn on unusable