Elijah Newren writes:
> Hi Junio,
>
> On Sun, Apr 29, 2018 at 8:25 PM, Junio C Hamano wrote:
>> * en/rename-directory-detection-reboot (2018-04-25) 36 commits
>
>>
>> Reboot of an attempt to detect wholesale directory renames and use
>> it while merging.
>>
>> Will merge to 'next'.
>
> Usual
Hi Junio,
On Sun, Apr 29, 2018 at 8:25 PM, Junio C Hamano wrote:
> * en/rename-directory-detection-reboot (2018-04-25) 36 commits
>
> Reboot of an attempt to detect wholesale directory renames and use
> it while merging.
>
> Will merge to 'next'.
Usually you have a mini-release-note in your
On 04/30, Junio C Hamano wrote:
> * bw/protocol-v2 (2018-03-15) 35 commits
> (merged to 'next' on 2018-04-11 at 23ee234a2c)
> + remote-curl: don't request v2 when pushing
> + remote-curl: implement stateless-connect command
> + http: eliminate "# service" line when using protocol v2
> + http:
Johannes Schindelin writes:
>> As I wrote elsewhere, for a low-impact and ralatively old issue like
>> this, it is OK for a fix to use supporting code that only exists in
>> more recent codebase and become unmergeable to anything older than
>> the concurrent 'maint' track as of the time when the
Hi Junio,
On Wed, 2 May 2018, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > So the problem you found is not a problem with *my* branch, of course, as
> > I did not fork off of ...
>
> Correct; there is no blame on you with the choice of the base. It
> was my mistake that I didn't
Johannes Schindelin writes:
> So the problem you found is not a problem with *my* branch, of course, as
> I did not fork off of ...
Correct; there is no blame on you with the choice of the base. It
was my mistake that I didn't check if the series could be queueable
on the maintenance track that
SZEDER Gábor writes:
> On Mon, Apr 30, 2018 at 5:25 AM, Junio C Hamano wrote:
>> * js/rebase-i-clean-msg-after-fixup-continue (2018-04-30) 4 commits
>> - rebase --skip: clean up commit message after a failed fixup/squash
>> - sequencer: always commit without editing when asked for
>> - reb
On Tue, May 01 2018, Johannes Schindelin wrote:
> I wonder whether `-!p` would be better/feasible?
In *nix shells `git -!p ...` unquoted will turn that !p into whatever
command you last ran that started with a "p", in my case `git -ping
8.8.8.8`. So there's a reason that's not the idiom in any *
On Tue, May 1, 2018 at 10:58 AM, Johannes Sixt wrote:
> Am 01.05.2018 um 13:57 schrieb Johannes Schindelin:
>> On Mon, 30 Apr 2018, Johannes Sixt wrote:
>>> Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
* js/no-pager-shorthand (2018-04-25) 1 commit
- git: add -N as a short option for
Am 01.05.2018 um 13:57 schrieb Johannes Schindelin:
Hi Hannes,
On Mon, 30 Apr 2018, Johannes Sixt wrote:
Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
* js/no-pager-shorthand (2018-04-25) 1 commit
- git: add -N as a short option for --no-pager
"git --no-pager cmd" did not have short-a
Hi,
On Mon, 30 Apr 2018, SZEDER Gábor wrote:
> On Mon, Apr 30, 2018 at 5:25 AM, Junio C Hamano wrote:
> > * js/rebase-i-clean-msg-after-fixup-continue (2018-04-30) 4 commits
> > - rebase --skip: clean up commit message after a failed fixup/squash
> > - sequencer: always commit without editin
Hi Hannes,
On Mon, 30 Apr 2018, Johannes Sixt wrote:
> Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
> > * js/no-pager-shorthand (2018-04-25) 1 commit
> > - git: add -N as a short option for --no-pager
> >
> > "git --no-pager cmd" did not have short-and-sweet single letter
> > option. Now
Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
* js/no-pager-shorthand (2018-04-25) 1 commit
- git: add -N as a short option for --no-pager
"git --no-pager cmd" did not have short-and-sweet single letter
option. Now it does.
Will merge to 'next'.
I consider your argument that -N is on
On Mon, Apr 30, 2018 at 5:25 AM, Junio C Hamano wrote:
> * js/rebase-i-clean-msg-after-fixup-continue (2018-04-30) 4 commits
> - rebase --skip: clean up commit message after a failed fixup/squash
> - sequencer: always commit without editing when asked for
> - rebase -i: Handle "combination o
What's cooking in git.git (Apr 2018, #04; Mon, 30)
--
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next&#
15 matches
Mail list logo
