Draft of Git Rev News edition 16

Hi, A draft of a new Git Rev News edition is available here: https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-16.md Everyone is welcome to contribute in any section either by editing the above page on GitHub and sending a pull request, or by commenting on this GitHub

[GIT PULL] l10n updates for 2.9.0 rc0

Hi Junio, Please pull the following git l10n updates. The following changes since commit 3a0f269e7c82aa3a87323cb7ae04ac5f129f036b: Git 2.9-rc0 (2016-05-23 15:02:48 -0700) are available in the git repository at: git://github.com/git-l10n/git-po tags/l10n-2.9.0-rc0 for you to fetch changes

Re: [PATCHv4] Documentation: triangular workflow

From: "Ramkumar Ramachandra" Junio C Hamano wrote: Jordan DE GEA wrote: > +* Allows contributors to work with Git even though they do not have > +write access to **UPSTREAM**. > > +* Allows maintainers to receive code from contributors they may not > +trust. Triangular

Re: [PATCHv4] Documentation: triangular workflow

From: "Junio C Hamano" "Philip Oakley" writes: +Preparation +~~~ + +Cloning from **PUBLISH**, which is a fork of **UPSTREAM** or an empty +repository. I agree here. To clone the upstream, to which you have no push access (by definition),

Re: [PATCHv4] Documentation: triangular workflow

Junio C Hamano wrote: > Jordan DE GEA wrote: > > > +* Allows contributors to work with Git even though they do not have > > +write access to **UPSTREAM**. > > > > +* Allows maintainers to receive code from contributors they may not > > +trust. Triangular workflow is the ability to accept changes

Re: [PATCH] Gitk Inotify support

>From 74d2f4c1ec560b358fb50b8b7fe8282e7e1457b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20Sch=C3=BCller?= Date: Thu, 9 Jun 2016 22:54:43 +0200 Subject: [PATCH] first support for inotify MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8

Re: [PATCH 1/2] bisect--helper: `is_expected_rev` shell function in C

Hey Eric, On Sat, Jun 11, 2016 at 12:44 AM, Eric Sunshine wrote: > On Fri, Jun 10, 2016 at 9:39 AM, Pranit Bauva wrote: >> On Fri, Jun 10, 2016 at 3:03 AM, Eric Sunshine >> wrote: >>> On Wed, Jun 8, 2016 at 11:24 AM,

Re: feature request: git svn dommit --preserve-timestamps

Peter Münster wrote: > On Sat, Jun 11 2016, Eric Wong wrote: > > > The git log after dcommit is tied to the SVN log, > > so git-svn can only reflect changes which appear in SVN. > > You mean, it's impossible, to keep the original timestamps?? It might be; just not easy; and I

Re: [PATCH v6 31/44] run-command: make dup_devnull() non static

On Sat, Jun 11, 2016 at 10:17 AM, Johannes Sixt wrote: > Am 10.06.2016 um 22:11 schrieb Christian Couder: >> >> --- a/run-command.c >> +++ b/run-command.c >> @@ -85,7 +85,7 @@ static inline void close_pair(int fd[2]) >> } >> >> #ifndef GIT_WINDOWS_NATIVE >> -static inline void

Re: [PATCH v6 43/44] builtin/apply: add a cli option for be_silent

On Fri, Jun 10, 2016 at 10:59 PM, René Scharfe wrote: > Am 10.06.2016 um 22:11 schrieb Christian Couder: >> >> Let's make it possible to request a silent operation on the >> command line. >> >> Signed-off-by: Christian Couder >> --- >> builtin/apply.c | 2

Re: [PATCH v6 41/44] am: use be_silent in 'struct apply_state' to shut up applying patches

On Sat, Jun 11, 2016 at 12:07 AM, Junio C Hamano wrote: > The update in 33/44 to make am call into apply that is not ready to > be called (e.g. the caller needs the dup(2) dance with /dev/null to > be silent) gets finally corrected with this step, which makes the > progress of

Re: [PATCH v6 31/44] run-command: make dup_devnull() non static

Am 10.06.2016 um 22:11 schrieb Christian Couder: --- a/run-command.c +++ b/run-command.c @@ -85,7 +85,7 @@ static inline void close_pair(int fd[2]) } #ifndef GIT_WINDOWS_NATIVE -static inline void dup_devnull(int to) +void dup_devnull(int to) I'm not adding arguments to what we've heard

Re: [PATCH v2 00/94] libify apply and use lib in am

Hi Hannes, On Fri, 10 Jun 2016, Johannes Sixt wrote: > Am 10.06.2016 um 13:11 schrieb Johannes Schindelin: > > On Fri, 10 Jun 2016, Christian Couder wrote: > > > > > I fixed this by moving the "close(fd)" call just after the > > > "apply_patch()" call. > > This bug in v1 was discovered by the

Re: feature request: git svn dommit --preserve-timestamps

On Sat, Jun 11 2016, Eric Wong wrote: > The git log after dcommit is tied to the SVN log, > so git-svn can only reflect changes which appear in SVN. You mean, it's impossible, to keep the original timestamps?? > Sidenote: The convention is reply-to-all on lists like > this one