Adam Brewster wrote: >> [...] >>> Then you can add the objects in the bundle to the basis, so they won't >>> get included in the next pack like this: >>> >>> $ git-basis --update my-basis < my-bundle >> >> Why not use "$(git ls-remote my-bundle)" somewhere in the invocation >> creating new bundle instead? >> > > You could use "git ls-remote my-bundle | git-basis --update my-basis" > to do the same thing as the command I gave above. I was thinking about $ git bundle create my-bundle --all --not $(git ls-remote my-bundle | cut -f1) (or `--branches' instead of `--all'). Or, if you don't want to keep bundle, but only save basis, just use $ git bundle create my-bundle --all --not $(git basis --show my-basis) No need for `--stdin' / `--revs' / `--basis' option to git-bundle, at the cost of little shell trickery. Or even $ git ls-remote my-bundle | cut -f1 > my-bases [...] $ git bundle create my-bundle --all --not $(cat my-bases) >>> I'm sure that my implementation is crap, but I think this is a useful >>> idea. Anybody agree? Disagree? >> >> Documentation, please? Especially that it looks like '--stdin' option >> is a bit tricky... > > I wanted to test the waters and make sure that someone was at least > vaguely interested in this (no need to document code that is never > going to leave my machine). See above example, to check if this would be enough... > I'll prepare another patch with documentation and changing --stdin to > --revs when I get a chance. I'm not sure if another name, like --bases=<filename / basename> wouldn't be better. Perhaps --stdin is a good name... -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
