git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Peter Baumann <waste.manager@gmx.de>, git@vger.kernel.org
Subject: Re: git-svn branch naming question
Date: Sun, 9 Dec 2007 03:25:06 +0100	[thread overview]
Message-ID: <20071209022505.GO3199@genesis.frugalware.org> (raw)
In-Reply-To: <20071209021336.GA8327@atjola.homenet>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

On Sun, Dec 09, 2007 at 03:13:36AM +0100, Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
> >         url = svn+ssh://vmiklos@svn.gnome.org/svn/ooo-build
> >         fetch = trunk:refs/master
> >         branches = branches/*:refs/*
> >         tags = tags/*:refs/tags/*
> 
> Just a guess, but this seems pretty headless ;-)

oh, right. here is my fixed config:

[svn-remote "svn"]
        url = svn+ssh://vmiklos@svn.gnome.org/svn/ooo-build
        fetch = trunk:refs/heads/master
        branches = branches/*:refs/heads/*
        tags = tags/*:refs/tags/*

git svn fetch still does not seem to do anything :S

thanks,
- VMiklos

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-12-09  2:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  1:04 git-svn branch naming question Miklos Vajna
2007-12-08 10:59 ` Peter Baumann
2007-12-08 14:14   ` Miklos Vajna
2007-12-08 16:56     ` Peter Baumann
2007-12-08 23:52       ` Miklos Vajna
2007-12-09  2:05         ` Miklos Vajna
2007-12-09  2:13           ` Björn Steinbrink
2007-12-09  2:25             ` Miklos Vajna [this message]
2007-12-09  2:26           ` Eric Wong
2007-12-09  2:36             ` Miklos Vajna
2007-12-09  3:26               ` Eric Wong
2007-12-09  5:16                 ` Harvey Harrison
2007-12-09 19:36                 ` Miklos Vajna

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=20071209022505.GO3199@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=waste.manager@gmx.de \
    /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).