git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: git-svn: fix example for centralized SVN clone

From
EWEric Wong <normalperson@yhbt.net>
Date
Nov 10, 2008, 01:12 UTC
Message-ID
<20081110011232.GA11666@hand.yhbt.net>
In-Reply-To
<20081109230012.47adbb32@perceptron>
Jan Krüger <jk@jk.gs> wrote:
Show 10 quoted lines
> The example that tells users how to centralize the effort of the initial
> git svn clone operation doesn't work properly. It uses rebase but that
> only works if HEAD exists. This adds one extra command to create a
> somewhat sensible HEAD that should work in all cases.
> 
> Signed-off-by: Jan Krüger <jk@jk.gs>
> ---
> I have a feeling this looks a bit ugly, but I can't think of a simpler
> solution (especially since we're not fetching the central repo's HEAD).
> Still, it's certainly better than a broken example.
*shrug*  Seems alright with me.
Adam wrote the original example, maybe he knows better.
Show 18 quoted lines
>  Documentation/git-svn.txt |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
> index 84c8f3c..ba94cd1 100644
> --- a/Documentation/git-svn.txt
> +++ b/Documentation/git-svn.txt
> @@ -544,6 +544,8 @@ have each person clone that repository with 'git-clone':
>         git remote add origin server:/pub/project
>         git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*'
>         git fetch
> +# Create a local branch from one of the branches just fetched
> +       git checkout -b master FETCH_HEAD
>  # Initialize git-svn locally (be sure to use the same URL and -T/-b/-t options as were used on server)
>         git svn init http://svn.example.com/project
>  # Pull the latest changes from Subversion
> --
> 1.6.0.3.578.g6a50
-- 
Eric Wong
Previous: Jan Krüger
Message 2 of 2 in “Documentation: git-svn: fix example for centralized SVN clone”
  1. Documentation: git-svn: fix example for centralized SVN cloneJan Krüger, Nov 9, 2008
  2. Eric WongNov 10, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.