From: Sverre Rabbelier <srabbelier@gmail.com>
To: carlos.duclos@nokia.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] git-archive: Add new option "--output" to write archive to a file instead of stdout.
Date: Mon, 16 Feb 2009 18:59:33 +0100 [thread overview]
Message-ID: <bd6139dc0902160959h689470e3mf55407bc24c96816@mail.gmail.com> (raw)
In-Reply-To: <599636D7828020419E3AB2DE5CCC8130036BF8B1D5@NOK-EUMSG-02.mgdnok.nokia.com>
Heya,
On Mon, Feb 16, 2009 at 18:37, <carlos.duclos@nokia.com> wrote:
> When archiving a repository there is no way to specify a file as output.
> This patch adds a new option "--output" that redirects the output to a file
> instead of stdout.
>
> Signed-off by: Carlos Manuel Duclos Vergara <carlos.duclos@nokia.com>
> ---
>
> NOTE: I can only use a webmail client, so some of the tabs might
> have overwritten by it. If that's the case I'll resend the patch as
> MIME attachment.
>
> Documentation/git-archive.txt | 3 +
> archive-zip.c | 1 -
> archive.c | 17 +++++
> t/t0024-crlf-archive.sh | 19 +++++
> t/t5000-tar-tree.sh | 148 +++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 187 insertions(+), 1 deletions(-)
Fixed that for ya :).
Anything that should not go in the commit message should go after the
triple dashes. Also, please wrap your lines at 80 characters. If your
web-client does not support this, please do so manually.
For your convenience, here is a line of 79 characters:
-------------------------------------------------------------------------------
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-02-16 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 17:37 [PATCH v2] git-archive: Add new option "--output" to write archive to a file instead of stdout carlos.duclos
2009-02-16 17:59 ` Sverre Rabbelier [this message]
2009-02-16 20:11 ` René Scharfe
2009-02-16 21:38 ` Junio C Hamano
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=bd6139dc0902160959h689470e3mf55407bc24c96816@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=carlos.duclos@nokia.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).