From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Daniele Segato <daniele.bilug@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: how to skip branches on git svn clone/fetch when there are errors
Date: Mon, 7 Sep 2009 17:53:21 +0200 [thread overview]
Message-ID: <4d8e3fd30909070853u6f4bc179qac96edae5c83a864@mail.gmail.com> (raw)
In-Reply-To: <9accb4400909070634oee46b78g9270586a2b0eb4b9@mail.gmail.com>
On Mon, Sep 7, 2009 at 3:34 PM, Daniele Segato<daniele.bilug@gmail.com> wrote:
[...]
Ciao Daniele,
> From e8a1a12e83b3f0b18ce842190d8fc8eddaa77f68 Mon Sep 17 00:00:00 2001
> From: Daniele Segato <daniele.bilug@gmail.com>
> Date: Mon, 7 Sep 2009 15:30:14 +0200
> Subject: [PATCH] Ignore error 175007 authorization failed on checkpath
>
> I don't know if this is the best solution to solve the issue but it does
> let me download the repo skipping the problematics paths
Usually these lines are for the commit message, I guess you don't want
to store these two lines in git.git :-)
> ---
So if you want to add comments like you did, write them after the 3
minus and before the content of the patch.
> git-svn.perl | 16 ++++++++++++++++
> 1 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/git-svn.perl b/git-svn.perl
> index a366c89..0ab6453 100755
Ciao,
--
Paolo
next prev parent reply other threads:[~2009-09-07 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 8:26 how to skip branches on git svn clone/fetch when there are errors Daniele Segato
2009-09-05 6:16 ` Eric Wong
2009-09-05 8:55 ` Daniele Segato
2009-09-06 1:48 ` Eric Wong
2009-09-07 9:30 ` Daniele Segato
2009-09-07 13:34 ` Daniele Segato
2009-09-07 13:53 ` Daniele Segato
2009-09-07 15:53 ` Paolo Ciarrocchi [this message]
2009-09-07 17:55 ` Daniele Segato
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=4d8e3fd30909070853u6f4bc179qac96edae5c83a864@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=daniele.bilug@gmail.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).