Git development
 help / color / mirror / Atom feed
From: "Tor Arvid Lund" <torarvid@gmail.com>
To: "Junio C Hamano" <junio@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #04; Sun, 17)
Date: Sun, 17 Aug 2008 13:44:05 +0200	[thread overview]
Message-ID: <1a6be5fa0808170444n74e498eob800ade8de79cbe@mail.gmail.com> (raw)
In-Reply-To: <7vej4o6j40.fsf@gitster.siamese.dyndns.org>

Hi,

On Sun, Aug 17, 2008 at 12:17 PM, Junio C Hamano <junio@pobox.com> wrote:
> [On Hold and/or Cooking]
>
> * ak/p4 (Thu Aug 14 23:40:39 2008 +0100) 14 commits
>  + Utilise our new p4_read_pipe and p4_write_pipe wrappers
>  + Add p4 read_pipe and write_pipe wrappers
>  + Put in the two other configuration elements found in the source
>  + Put some documentation in about the parameters that have been
>   added
>  + Move git-p4.syncFromOrigin into a configuration parameters section
>  + Consistently use 'git-p4' for the configuration entries
>  + If the user has configured various parameters, use them.
>  + Switch to using 'p4_build_cmd'
>  + If we are in verbose mode, output what we are about to run (or
>   return)
>  + Add a single command that will be used to construct the 'p4'
>   command
>  + Utilise the new 'p4_system' function.
>  + Have a command that specifically invokes 'p4' (via system)
>  + Utilise the new 'p4_read_pipe_lines' command
>  + Create a specific version of the read_pipe_lines command for p4
>   invocations
>
> Warmly received by the primary contributor of git-p4; I do not mind
> merging this before 1.6.0 (final call for "Yays").

I've tried these for a few days now, and they work fine for me, so FWIW: Yay!

-Tor Arvid-

  reply	other threads:[~2008-08-17 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 10:17 What's cooking in git.git (Aug 2008, #04; Sun, 17) Junio C Hamano
2008-08-17 11:44 ` Tor Arvid Lund [this message]
2008-08-18 22:41 ` Brian Downing

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=1a6be5fa0808170444n74e498eob800ade8de79cbe@mail.gmail.com \
    --to=torarvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox