From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: Paul Campbell <pcampbell@kemitix.net>
Cc: git@vger.kernel.org
Subject: Re: Questions/investigations on git-subtree and tags
Date: Thu, 7 Mar 2013 13:50:11 +0100 (CET) [thread overview]
Message-ID: <1721159119.197038.1362660611167.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CALeLG_k=8S0Q-89CUvNPQT91gkJm1NdDN6YtCkdTQZZi9RUjWA@mail.gmail.com>
> >>
> >> Git subtree ignores tags from the remote repo.
> >>
> >
> > is that a design decision or a case of "not implemented yet"
>
> I'm not sure. If you imported all the tags from all your subtrees
> repos, you could easily end up with duplicate tags from different
> repos. They could be namespaced, but there is no concept of namespace
> in git-subtree. That even assumes that you can tag a subtree (I've
> not
> tried).
>
Ok, I can understand that you don't want to import tags for namespace reason, but in that case shouldn't
git subtree add refuse to create a subtree when the tag isn't a commit
or if it allows it, what would be the gracefull way to handle that ?
i'm quite new to git's internals, so I don't really know if/what the right approch would be.
note that all those problems seems to disapear when squash is not used
next prev parent reply other threads:[~2013-03-07 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1492019317.191838.1362650820122.JavaMail.root@openwide.fr>
2013-03-07 10:25 ` Questions/investigations on git-subtree and tags Jeremy Rosen
2013-03-07 11:00 ` Paul Campbell
2013-03-07 11:05 ` Jeremy Rosen
2013-03-07 12:02 ` Paul Campbell
2013-03-07 12:50 ` Jeremy Rosen [this message]
2013-03-07 15:00 ` Paul Campbell
2013-03-07 15:15 ` Jeremy Rosen
2013-03-07 15:29 ` Paul Campbell
2013-03-07 16:09 ` Jeremy Rosen
2013-03-08 16:29 ` Jeremy Rosen
2013-03-08 17:23 ` Junio C Hamano
2013-03-08 17:29 ` Jeremy Rosen
2013-03-12 10:02 ` Jeremy Rosen
2013-03-12 23:57 ` Paul Campbell
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=1721159119.197038.1362660611167.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--cc=git@vger.kernel.org \
--cc=pcampbell@kemitix.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.