From: Jan Hudec <bulb@ucw.cz>
To: Sebastian Harl <sh@tokkee.org>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Sam Granieri Jr" <sjgdev@gmail.com>,
"Git Users List" <git@vger.kernel.org>
Subject: Re: [Feature Request] Better Subversion integration
Date: Fri, 15 Feb 2008 23:38:17 +0100 [thread overview]
Message-ID: <20080215223817.GA13178@efreet.light.src> (raw)
In-Reply-To: <20080211084704.GB20741@albany.tokkee.org>
On Mon, Feb 11, 2008 at 09:47:04 +0100, Sebastian Harl wrote:
> Hi,
>
> On Sun, Feb 10, 2008 at 04:56:11AM +0100, Björn Steinbrink wrote:
> > SVN tags aren't like git tags. A "tag" in SVN is just another directory,
> > which you can modify at will.
>
> Well, a SVN tag could be represented as a Git branch _and_ a Git tag
> pointing to the head of that branch. Whenever any such "tag branch"
> advances, the user should be notified, the user responsible for the
> further commits to the SVN "tag" should be seriously hurt and the Git
> tag should be overwritten (git tag -f).
There's no need to have a Git _branch_ together with the tag -- tag is also
a ref.
For the rest, the user definitely has to be notified, because git push will
_not_ push out the updated tag if the previous version of it was already
pushed. So the user will have to deal with that manually.
If there was to be a support for tags in git-svn, I would actually suggest to
simply make the name mapping more flexible and simply say, that branches in
tags/ should be imported to refs/tags (while the rest going to
refs/remotes/svn). You see, subversion tags are not annotated (so they don't
need special handling) and git-update-ref will update tags just fine.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
prev parent reply other threads:[~2008-02-15 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 2:44 [Feature Request] Better Subversion integration Sam Granieri Jr
2008-02-10 3:56 ` Björn Steinbrink
2008-02-10 16:52 ` Michael Haggerty
2008-02-10 17:53 ` Björn Steinbrink
2008-02-10 19:36 ` Michael Haggerty
2008-02-10 22:18 ` Björn Steinbrink
2008-02-11 8:47 ` Sebastian Harl
2008-02-11 16:55 ` Sam Granieri Jr
2008-02-11 22:11 ` Sebastian Harl
2008-02-15 22:38 ` Jan Hudec [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=20080215223817.GA13178@efreet.light.src \
--to=bulb@ucw.cz \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=sh@tokkee.org \
--cc=sjgdev@gmail.com \
/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).