All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Diamand <luke@diamand.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2018, #03; Wed, 23)
Date: Thu, 24 May 2018 20:50:09 +0100	[thread overview]
Message-ID: <CAE5ih7-MbHLjK+GaxpfAZgkyuzN=OWs0wsLdKTXLK64CeFe0_Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqwovtudia.fsf@gitster-ct.c.googlers.com>

On 24 May 2018 at 01:02, Junio C Hamano <gitster@pobox.com> wrote:
> 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.
>
> 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
>




>
>
> * ld/p4-unshelve (2018-05-23) 3 commits
>  - git-p4: unshelve: use action==add instead of rev==none
>  - SQUASH???
>  - git-p4: add unshelve command
>
>  "git p4" learned to "unshelve" shelved commit from P4.
>
>  Expecting a reroll.
>  cf. <CAE5ih7_jgrTXv25hYqoq=95H0zArbJAeQO3gO_TRpyLHGfTWUg@mail.gmail.com>
>

I've sent a rereroll which contains the various fixes, and removes the
extraneous verbose print change (since that's being covered
elsewhere).

Luke

  parent reply	other threads:[~2018-05-24 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  0:02 What's cooking in git.git (May 2018, #03; Wed, 23) Junio C Hamano
2018-05-24  6:39 ` Elijah Newren
2018-05-28  5:34   ` Junio C Hamano
2018-05-24 19:09 ` Stefan Beller
2018-05-24 19:42 ` Ævar Arnfjörð Bjarmason
2018-05-24 19:50 ` Luke Diamand [this message]
2018-05-25 12:31 ` js/empty-config-section-fix, was " Johannes Schindelin
2018-05-28  5:40   ` Junio C Hamano
2018-05-28 11:20     ` Johannes Schindelin
2018-05-29 16:49       ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE5ih7-MbHLjK+GaxpfAZgkyuzN=OWs0wsLdKTXLK64CeFe0_Q@mail.gmail.com' \
    --to=luke@diamand.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.