Skip to content

examples: Free the git_config and git_config_entry after use - #6071

Merged
ethomson merged 1 commit into
libgit2:mainfrom
257:examples
Sep 27, 2021
Merged

examples: Free the git_config and git_config_entry after use#6071
ethomson merged 1 commit into
libgit2:mainfrom
257:examples

Conversation

@257

@257 257 commented Sep 23, 2021

Copy link
Copy Markdown
Contributor

No description provided.

@257
257 force-pushed the examples branch 3 times, most recently from 6b75afd to 9b7ca64 Compare September 24, 2021 18:11
@ethomson
ethomson merged commit 424812e into libgit2:main Sep 27, 2021
@ethomson

Copy link
Copy Markdown
Member

Good catch! Thanks for the fix. 😀

@257

257 commented Sep 27, 2021 via email

Copy link
Copy Markdown
Contributor Author

@ethomson

Copy link
Copy Markdown
Member

I'm not sure what you mean.

Screen Shot 2021-09-27 at 16 07 17

Your commit has your committer and author information, which is what you pushed up:

% git cat-file commit 581cfbd
tree 48803cd33cc63c03015446332b04789b3a9e81a7
parent 136901086ecfdd2b5cc106782310355a9c0b1a9a
author Paymon MARANDI <darwinskernel@gmail.com> 1632412792 -0400
committer jrun <darwinskernel@gmail.com> 1632507299 -0400

@257

257 commented Sep 27, 2021

Copy link
Copy Markdown
Contributor Author

git cat-file commit 581cfbd

i see, thanks. i was looking at git cat-file commit 424812e3d874.
actually you're doing it different from others; what's the workflow here, i mean if you have time to explain.

@ethomson

Copy link
Copy Markdown
Member

I'm not really doing anything special - 424812e is the merge commit that brought your pull request branch into main. This is the default way pull requests get merged in GitHub - and the equivalent to if I had merged it by running git merge <your branch name>. The person who runs git merge is marked as the committer and author of the merge commit that puts the code into the main branch.

If you've seen other behaviors, it may be that people had a rebase or squash based workflow enabled. I don't like those, personally, so I just stick with the GitHub defaults.

@257

257 commented Sep 27, 2021 via email

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants