From: Pascal Obry <pascal@obry•net>
To: Avery Pennarun <apenwarr@gmail•com>
Cc: Git Mailing-List <git@vger•kernel.org>
Subject: Re: git-svn branches creation question
Date: Thu, 26 Jun 2008 21:05:22 +0200 [thread overview]
Message-ID: <4863E872.4070904@obry.net> (raw)
In-Reply-To: <32541b130806260908m7ca2060bub071da52aa7a33ce@mail.gmail.com>
Avery,
> And creating branches in svn is a single command, even if you don't
> have an svn checkout:
>
> svn cp $SVN/trunk $SVN/branches/whatever
That's what I'm doing as I said in my message.
> So it seems unnecessary to duplicate this feature in git.
Well it would be quite handy to work on Git directly (eventually
off-line) and doing the final "git svn dcommit" to update the subversion
repository and creating the branches if necessary.
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
prev parent reply other threads:[~2008-06-26 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 15:55 git-svn branches creation question Pascal Obry
2008-06-26 16:08 ` Avery Pennarun
2008-06-26 19:05 ` Pascal Obry [this message]
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=4863E872.4070904@obry.net \
--to=pascal@obry$(echo .)net \
--cc=apenwarr@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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