Dear all,
I have a basic SVN repo with a few tags marking code releases organised the
following way:
/src
/releases
/0.1
/0.2
/0.3
Where *src* is the trunk and all sub-folders of *releases* are tags created
with *svn copy*. I've managed to migrate this repo using *git svn*,
On Tuesday, January 22, 2013 11:11:00 AM UTC+1, Luís de Sousa wrote:
Dear all,
I have a basic SVN repo with a few tags marking code releases organised
the following way:
/src
/releases
/0.1
/0.2
/0.3
Where *src* is the trunk and all sub-folders of *releases* are
On Tuesday, 22 January 2013 13:10:02 UTC+1, Konstantin Khomoutov wrote:
Hence git-svn creates one remote branch in your local repository for
each tag in the Subversion repository.
Hi Konstatin, thanks for the reply.
As I wrote initially, *git svn clone* doesn't create any branches:
$ git
On Tue, 22 Jan 2013 04:53:30 -0800 (PST)
Luís de Sousa luis.a.de.so...@gmail.com wrote:
Hence git-svn creates one remote branch in your local repository
for each tag in the Subversion repository.
[...]
As I wrote initially, *git svn clone* doesn't create any branches:
$ git branch -r
On Tuesday, January 22, 2013 12:11:19 PM UTC+1, Thomas Ferris Nicolaisen
wrote:
Yes. If it's possible in SVN, then it ideally should be handled by
git-svn. Just make sure you have the latest version of git to make sure
this hasn't been fixed in recent versions. It has at least been
On Tue, 22 Jan 2013 05:44:17 -0800 (PST)
Luís de Sousa luis.a.de.so...@gmail.com wrote:
[...]
Now the issue is that I have no master branch, but all the oldre
branches cloned. Can I just rename the most recent branch and delete
the older branches?
This is a rather philosophical question. The
On Tue, Jan 22, 2013 at 10:14:12PM -0800, Rahul Gupta wrote:
This is probably a hangover from SVN habits but still I would like the Git
way doing this.
Normally using SVN, when I work on a latex file, I store the pdf generated
in my Tag folder along with latex file. There is no concept of
