git branches (was: A question for you all: size_t or unsigned int)

Paul Harris paulharris at computer.org
Thu Nov 13 14:12:24 UTC 2008


2008/11/13 martin f krafft <madduck at debian.org>

> also sprach Paul Harris <paulharris at computer.org> [2008.11.13.1448 +0100]:
> > Attached are 3 patches, you clone the git repo and then use "git
> > am" to apply each one in turn (Martin already knows this,
> > I didn't)
>
> A better way to share those would probably be a branch you publish.
> So you could e.g.
>
>  git checkout -b paulharris/some-name
>
> then apply/am/cherry-pick the commits that are part of "some-name"
> (you might want to make more than one branch) into the branch and
> push it (git push origin paulharris/some-name).
>
> Then, people can just do
>
>  git fetch origin
>  git checkout -b paulharris/some-name origin/paulharris/some-name
>
> to try it out.
>
> If you have those three patches on top of origin/master right now,
> so that your master is three commits ahead from origin/master, then
> you could do this:
>
>  git checkout -b paulharris/feature1 master
>  git cherry-pick <commit belonging to feature1> <another commit>
>  git checkout -b paulharris/feature2 master
>  git cherry-pick <commit belonging to feature2>
>


i tried this and stuffed it up.  my patches are one-after-the-other and
there is a fair bit of overlap, so I thought i'd start with just 1 branch
...

git clone etc
cd libkdtree
git checkout -b paulharris/bugfixes master
git am ../0001
git am ../0002
git am ../0002

so all looks good... now what?
git push says "everything up-to-date"

? i just don't get git ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/libkdtree-devel/attachments/20081113/e115e752/attachment.htm 


More information about the libkdtree-devel mailing list