Wierd... well, 'git push' seems to have done it. I don't understand why
it hadn't got there before...
cheers
Miller
On 7/31/25 9:08 AM, IOhannes m zmoelnig via Pd-dev wrote:
On 7/30/25 18:02, Miller Puckette via Pd-dev wrote:
I _think_ the master branch is pushed to github - and ci sees it too
(tagged 0.56-0).
it seems you pushed the tag, but not the (master) branch.
at least right now github shows me:
- the `master` branch is at revision [7cc62491]
- the `0.56-0` tag is at revision [0e0ce5bf]
see also <https://github.com/pure-data/pure-data/tree/master/> resp
<https://github.com/pure-data/pure-data/releases/tag/0.56-0>.
[7cc62491]
<https://github.com/pure-data/pure-data/commit/7cc624916fb796e2ee3dd2a698d6244c43951ab0>
[0e0ce5bf]
<https://github.com/pure-data/pure-data/commit/0e0ce5bf4b24367aae64680e1f1733e0970f30cd>
however, i noticed now, that it seems you did push the `master` branch
to sourceforge.
(<https://sourceforge.net/p/pure-data/pure-data/ci/master/tree/>)
and... I've started squash-mergine the documentation branch because
it has
far more frequent commits than other branches and the 'git log' is
hard to look
through for code changes.
fair enough.
as a side-note, you can tell git-log to only list those files you are
interested in:
```sh
git log -- src/`
```
or (as i just learned while writing this email), you could also tell
git-log to exclude certain directories (or files):
```sh
git log -- . ':!doc'
```
see <https://stackoverflow.com/questions/5685007/>
this also works for `gitk` (which i personally use for browing the git
history)
gfmadsrf
IOhannes
---
pd-dev@lists.iem.at - the Pd developers' mailinglist
https://lists.iem.at/hyperkitty/list/pd-dev@lists.iem.at/message/FSG6QPXZFVEMVGGHYH7JWJ4YXBNDFBF4/
---
pd-dev@lists.iem.at - the Pd developers' mailinglist
https://lists.iem.at/hyperkitty/list/pd-dev@lists.iem.at/message/MXC3BK2ABXBUV3KWUGNAJPWBFZAP7KDU/