Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments for PostgreSQL switches to Git #308

Open
phinjensen opened this issue Nov 11, 2017 · 7 comments
Open

Comments for PostgreSQL switches to Git #308

phinjensen opened this issue Nov 11, 2017 · 7 comments

Comments

@phinjensen
Copy link
Contributor

phinjensen commented Nov 11, 2017

Comments for https://www.endpointdev.com/blog/2010/05/postgresql-switches-to-git/
By Greg Sabino Mullane

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
@phinjensen
Copy link
Contributor Author

original author: David Christensen
date: 2010-05-19T17:16:59-04:00

So are they rebuilding the master repository, compared to the version they've had on git.postgresql.org, or keeping the incremental CVS import until switchover so $hackers don't have to be sad their SHA1s are all changing?

@phinjensen
Copy link
Contributor Author

original author: Greg Sabino Mullane
date: 2010-05-19T17:21:42-04:00

The hashes on git.postgresql.org will change. No way around that, but it's a very useful one-time pain!

@phinjensen
Copy link
Contributor Author

original author: Jon Jensen
date: 2010-05-19T18:36:05-04:00

The mailing list for commits with inline diffs would be easy enough to create on our own. I'm not sure what good commit notifications without diffs are, really. They either mean I have to manually go look up the diff, or I just don't and then there's less code review going on.

@phinjensen
Copy link
Contributor Author

original author: Greg Smith
date: 2010-05-20T01:42:32-04:00

At a minimum we can provide a gitweb URL, so that it's as simple as clicking on the link in the e-mail if you actually want to review the code. That doesn't risk sending out giant diffs and correspondingly bloating the mailing list, while still making it easy to see them if you want to.

@david: the swap from the current incrementally updated repo to a better quality one-time conversion is only going to happen at the switchover. So there will be a single bit of disruption that changes all the commit history, but you'll know it's coming long in advance, and the incremental one will be available until then.

@phinjensen
Copy link
Contributor Author

original author: Jon Jensen
date: 2010-05-20T11:59:20-04:00

Greg, yes, the URLs are nice, but in my experience code review happens much more when the diff is right there inline (not in an attachment, right inline). Even "huge" diffs are rarely all that huge, especially compared to some of the bloated HTML email kicking around the net these days. :)

In any case, it doesn't need to be either/or. It'd be easy to have one list that gets commit info + link only, and another that also gets inline diffs, so people can choose which they prefer.

The move to Git is great news, by the way!

@phinjensen
Copy link
Contributor Author

original author: Nicolas Marchildon
date: 2010-05-20T14:18:47-04:00

Anyone used Gerrit for code reviews?

@phinjensen
Copy link
Contributor Author

original author: Greg Sabino Mullane
date: 2010-05-24T09:17:06-04:00

Nicolas: Not in the Postgres community it seems. I've never heard anyone talk about it, and a mailing list search (http://postgresql.markmail.org/search/?q=gerrit) finds no relevant hits.

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

No branches or pull requests

1 participant