Paul, I'm not quite sure where I should go from here...
should I send you a patch so you make it a V3 of your patch ? should I
send a patch superseeding yours ?
I have also found a similar problem in git-subtree pull, which needs
the same fix.
in the mean time, attached is the current
On Tue, Mar 12, 2013 at 10:02 AM, Jeremy Rosen jeremy.ro...@openwide.fr wrote:
Paul, I'm not quite sure where I should go from here...
should I send you a patch so you make it a V3 of your patch ? should I
send a patch superseeding yours ?
I have also found a similar problem in git-subtree
ok, attached is a patch on top of your patch that solves my particular
problem
I am not formally submitting it since its on top of your part and i'd
really like your input before submitting.
It solves my problem and afaict does what your fix did and what git-subtree
originally intended to do...
Jeremy Rosen jeremy.ro...@openwide.fr writes:
506,513c506,507
case $2 in
*\**) # Avoid pulling in multiple branches
die '$2' contains a wildcard
;;
*:*) # Don't create a local branch for the subtree
- Mail original -
Jeremy Rosen jeremy.ro...@openwide.fr writes:
506,513c506,507
case $2 in
*\**) # Avoid pulling in multiple branches
die '$2' contains a wildcard
;;
*:*) # Don't create a local branch for
Hello everybody
I am trying to use git-subtree to follow a subproject but I have a couple of
problems and I am not sure if I am doing something wrong
Basically I am trying to use a tag on the subproject as my base for the
subproject but subtree doesn't seem to handle that properly
my first
On Thu, Mar 7, 2013 at 10:25 AM, Jeremy Rosen jeremy.ro...@openwide.fr wrote:
Hello everybody
I am trying to use git-subtree to follow a subproject but I have a couple of
problems and I am not sure if I am doing something wrong
Basically I am trying to use a tag on the subproject as my
Hi Jérémy,
Git subtree ignores tags from the remote repo.
is that a design decision or a case of not implemented yet
To follow a project in a subdirectory I would use git-subtree add
selecting a branch, not a tag, from the other repo. Then use
git-subtree pull to keep yourself
On Thu, Mar 7, 2013 at 11:05 AM, Jeremy Rosen jeremy.ro...@openwide.fr wrote:
Hi Jérémy,
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
On Thu, Mar 7, 2013 at 12:50 PM, Jeremy Rosen jeremy.ro...@openwide.fr wrote:
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
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
It shouldn't and tries not to, but is limited in it's ability to
identify if a refspec points to a commit or
On Thu, Mar 7, 2013 at 3:15 PM, Jeremy Rosen jeremy.ro...@openwide.fr wrote:
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
It shouldn't and tries not to,
I think I tried adding the ^{} syntax, but I don't think it works on
remote repos. Or I couldn't get the right syntax.
indeed, it doesn't work on fetch, but it could be used somewhere between the
fetch and the commit-tree to move from the ref to the associated commit
Latest patch:
13 matches
Mail list logo
