From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org
Subject: es/pathspec-f-f-grep, was Re: am/pathspec-f-f-checkout
Date: Fri, 6 Dec 2019 16:23:03 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1912061622220.31080@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1912061618440.31080@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Oops, I was talking about `es/pathspec-f-f-grep`, not about
`am/pathspec-f-f-checkout`, sorry for the mixup.
On Fri, 6 Dec 2019, Johannes Schindelin wrote:
> Hi Junio & Emily,
>
> On Thu, 5 Dec 2019, Junio C Hamano wrote:
>
> > * am/pathspec-f-f-checkout (2019-12-04) 7 commits
> > - checkout, restore: support the --pathspec-from-file option
> > - doc: restore: synchronize <pathspec> description
> > - doc: checkout: synchronize <pathspec> description
> > - doc: checkout: fix broken text reference
> > - doc: checkout: remove duplicate synopsis
> > - add: support the --pathspec-from-file option
> > - cmd_add: prepare for next patch
> > (this branch uses am/pathspec-from-file; is tangled with es/pathspec-f-f-grep.)
> >
> > A few more commands learned the "--pathspec-from-file" command line
> > option.
> >
> > Will merge to 'next'.
>
> Gábor noticed that this breaks Travis, and I provided a patch that
> initializes those new variables. Please squash that in before merging to
> `next`.
>
> Thanks,
> Dscho
next prev parent reply other threads:[~2019-12-06 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 22:36 What's cooking in git.git (Dec 2019, #02; Thu, 5) Junio C Hamano
2019-12-06 15:20 ` am/pathspec-f-f-checkout, was " Johannes Schindelin
2019-12-06 15:23 ` Johannes Schindelin [this message]
2019-12-06 16:27 ` es/pathspec-f-f-grep, was Re: am/pathspec-f-f-checkout Junio C Hamano
2019-12-06 15:52 ` ag/edit-todo-drop-check, Re: What's cooking in git.git (Dec 2019, #02; Thu, 5) Johannes Schindelin
2019-12-06 15:56 ` js/advise-rebase-skip, was " Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1912061622220.31080@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).