On 31-01-13 04:49, John Ralls wrote:
On Jan 30, 2013, at 6:44 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 28-01-13 18:44, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
Is that what's in place now (except to a stand-in repo on
code.gnucash.org instead of github)?
On 28-01-13 18:44, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
Is that what's in place now (except to a stand-in repo on
code.gnucash.org instead of github)?
There is no stand-in repo. The current end point is gitolite
I never imagined a stand-in repo. In retrospect I
Status update:
On 25-01-13 17:35, Derek Atkins wrote:
Just for the record, the things left to do are:
1) get gitolite to push to github -- this will require a github reset
Hook is ready. Whenever we reset github and set the proper origin
remotes in our gitolite repos, all changes will be
On Jan 30, 2013, at 6:44 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 28-01-13 18:44, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
Is that what's in place now (except to a stand-in repo on
code.gnucash.org instead of github)?
There is no stand-in repo. The current
Geert Janssens janssens-ge...@telenet.be writes:
In order to do so, you will have to configure gitolite to look for
hooks in the gitolite-admin repo. Here's a starting point:
http://sitaramc.github.com/gitolite/cust.html#hooks
http://sitaramc.github.com/gitolite/cust.html#pushcode
John Ralls jra...@ceridwen.us writes:
I guess the best way would be svn-gitolite-github, so when we drop svn
and start committing to gitolite directly we don't have to do anything.
That is how it is planned indeed. For completeness, I'll just point out that
the push to github (or any other
On 25-01-13 20:19, John Ralls wrote:
On Jan 25, 2013, at 9:43 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 25-01-13 18:12, Derek Atkins wrote:
I'm fine with this. I *may* have some time this weekend, but not a
lot. I promised I'd use this weekend to clean up my office so I wont
On Jan 26, 2013, at 2:04 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 25-01-13 20:19, John Ralls wrote:
On Jan 25, 2013, at 9:43 AM, Geert Janssens janssens-ge...@telenet.be
wrote:
On 25-01-13 18:12, Derek Atkins wrote:
I'm fine with this. I *may* have some time this weekend,
On 25-01-13 02:50, Yawar Amin wrote:
On 2013-01-23 10:21, Derek Atkins wrote:
[...]
Once that happens we'll get svn - gitolite - github automatically on
every commit (modulo the up-to-60s delay in the svn - gitolite
transfer). Then, down the road, once we turn off svn we'll still have
the
Geert Janssens janssens-ge...@telenet.be writes:
That's correct.
Pedantic Strictly speaking you could _try_ to push but the attempt
would fail due to insufficient permissions. That's because the
gitolite repos are configured read-only, and will remain so as long as
the svn-gitolite bridge
On Jan 25, 2013, at 8:35 AM, Derek Atkins warl...@mit.edu wrote:
Geert Janssens janssens-ge...@telenet.be writes:
That's correct.
Pedantic Strictly speaking you could _try_ to push but the attempt
would fail due to insufficient permissions. That's because the
gitolite repos are
On 25-01-13 17:35, Derek Atkins wrote:
Just for the record, the things left to do are:
1) get gitolite to push to github -- this will require a github reset
2) convert www to use git and get gitolite to signal an update instead
of svn
3) send emails from gitolite instead of svn
I think
On 25-01-13 17:57, John Ralls wrote:
On Jan 25, 2013, at 8:35 AM, Derek Atkins warl...@mit.edu wrote:
Geert Janssens janssens-ge...@telenet.be writes:
That's correct.
Pedantic Strictly speaking you could _try_ to push but the attempt
would fail due to insufficient permissions. That's
Geert Janssens janssens-ge...@telenet.be writes:
On 25-01-13 17:35, Derek Atkins wrote:
Just for the record, the things left to do are:
1) get gitolite to push to github -- this will require a github reset
2) convert www to use git and get gitolite to signal an update instead
of svn
3)
On 25-01-13 18:12, Derek Atkins wrote:
I'm fine with this. I *may* have some time this weekend, but not a
lot. I promised I'd use this weekend to clean up my office so I wont
really be online much.
I won't have time this weekend.
Also, I'll need some help with:
1) setting up the repos to
On Jan 25, 2013, at 9:43 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 25-01-13 18:12, Derek Atkins wrote:
I'm fine with this. I *may* have some time this weekend, but not a
lot. I promised I'd use this weekend to clean up my office so I wont
really be online much.
I won't have
On 2013-01-23 10:21, Derek Atkins wrote:
[...]
Once that happens we'll get svn - gitolite - github automatically on
every commit (modulo the up-to-60s delay in the svn - gitolite
transfer). Then, down the road, once we turn off svn we'll still have
the gitolite - github auto-push in place
On 2013-01-23 10:21, Derek Atkins wrote:
[...]
The next step will be to get gitolite to push to github, but we don't
want to set that up until everyone is ready to reset github.
I'm ready if everyone else is (git format-patch and am worked smoothly).
If anyone's curious:
$ cd $OLD_REPO_DIR
$
On 22-01-13 14:30, Derek Atkins wrote:
Geert Janssens janssens-ge...@telenet.be writes:
Another option would be to keep John's Jeeves set up to handle all
git-svn interaction until we can drop our svn set up completely.
The only change needed on John's server would be that it should push
all
On 23-01-13 01:43, John Ralls wrote:
On Jan 22, 2013, at 9:23 AM, John Ralls jra...@ceridwen.us wrote:
On Jan 22, 2013, at 9:00 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 22-01-13 17:41, John Ralls wrote:
On Jan 22, 2013, at 7:04 AM, Geert Janssens janssens-ge...@telenet.be
On Jan 23, 2013, at 2:31 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 22-01-13 14:30, Derek Atkins wrote:
Geert Janssens janssens-ge...@telenet.be writes:
Another option would be to keep John's Jeeves set up to handle all
git-svn interaction until we can drop our svn set up
On Jan 23, 2013, at 3:47 AM, Geert Janssens janssens-ge...@telenet.be wrote:
I have verified the procedure to work. Thanks. I did some very minor
modifications, which I hope clear up some small confusions.
Any suggestion to migrate the stashed stack ?
Sorry, what do you mean by
John Ralls jra...@ceridwen.us writes:
I realised this morning that the choice of (svn) URL is no longer
important. The main concern to keep the original URL was to preserve
the commit hashes. But due to the updates to the authors file, the
svn import into git will result in new hashes
John Ralls jra...@ceridwen.us writes:
On Jan 23, 2013, at 3:47 AM, Geert Janssens janssens-ge...@telenet.be wrote:
I have verified the procedure to work. Thanks. I did some very minor
modifications, which I hope clear up some small confusions.
Any suggestion to migrate the stashed stack
Yawar Amin yawar.a...@gmail.com writes:
Derek, svn2git is a recommended tool that uses git-svn to do the
conversion for you automatically. You just feed it an authors file
(which John has, I guess), tell it to split out the git repos from the
overarching svn repo, and let it do the work of
On 23-01-13 16:16, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
On Jan 23, 2013, at 3:47 AM, Geert Janssens janssens-ge...@telenet.be wrote:
I have verified the procedure to work. Thanks. I did some very minor
modifications, which I hope clear up some small confusions.
Any
On 23-01-13 15:37, John Ralls wrote:
On Jan 23, 2013, at 2:31 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 22-01-13 14:30, Derek Atkins wrote:
Geert Janssens janssens-ge...@telenet.be writes:
Another option would be to keep John's Jeeves set up to handle all
git-svn interaction
On 23-01-13 16:15, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
I realised this morning that the choice of (svn) URL is no longer
important. The main concern to keep the original URL was to preserve
the commit hashes. But due to the updates to the authors file, the
svn import
On Jan 23, 2013, at 7:39 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 23-01-13 16:16, Derek Atkins wrote:
John Ralls jra...@ceridwen.us writes:
On Jan 23, 2013, at 3:47 AM, Geert Janssens janssens-ge...@telenet.be
wrote:
I have verified the procedure to work. Thanks. I did
On 21-01-13 21:03, Yawar Amin wrote:
Hi Derek,
On 2013-01-21, at 9:11, Derek Atkins warl...@mit.edu wrote:
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't know how to
fix.
I don't know gitolite, but
Yawar Amin yawar.a...@gmail.com writes:
Hi Derek,
On 2013-01-21, at 9:11, Derek Atkins warl...@mit.edu wrote:
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't know how to
fix.
I don't know
Geert Janssens janssens-ge...@telenet.be writes:
Another option would be to keep John's Jeeves set up to handle all
git-svn interaction until we can drop our svn set up completely.
The only change needed on John's server would be that it should push
all updates to the gitolite repositories
On 22-01-13 14:20, Derek Atkins wrote:
Yawar Amin yawar.a...@gmail.com writes:
Hi Derek,
On 2013-01-21, at 9:11, Derek Atkins warl...@mit.edu wrote:
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't
That's ugly...
Chris Shoemaker is the name associated with svn name chris, so the
issue is indeed in the github repo.
I agree to restart from scratch on github. I also prefer correctness of
authorship.
I have a couple of local branches with commits not on github, but that
doesn't matter.
On 22-01-13 15:51, John Ralls wrote:
On Jan 22, 2013, at 5:30 AM, Derek Atkins warl...@mit.edu wrote:
Geert Janssens janssens-ge...@telenet.be writes:
Another option would be to keep John's Jeeves set up to handle all
git-svn interaction until we can drop our svn set up completely.
The only
Hi folks,
On 2013-01-22, at 9:51, John Ralls jra...@ceridwen.us wrote:
On Jan 22, 2013, at 5:30 AM, Derek Atkins warl...@mit.edu wrote:
[...]
Maybe.. Here's the bigger issue, if I found issues/bugs in John's
svn-git conversion, what do we do? (and yes, I found a problem in the
Hi Geert,
On 2013-01-22, at 10:04, Geert Janssens janssens-ge...@telenet.be wrote:
[...]
What steps would your recommend to reattach private branches ? With my
(limited) git knowledge I would only know how to export (git format-patch)
from the old repo and import (git am) in the new clone.
On Jan 22, 2013, at 7:01 AM, Geert Janssens janssens-ge...@telenet.be wrote:
That's ugly...
Chris Shoemaker is the name associated with svn name chris, so the issue is
indeed in the github repo.
I agree to restart from scratch on github. I also prefer correctness of
authorship.
I
Mike Evans mi...@saxicola.idps.co.uk writes:
Since I was expecting to have to do a fresh clone from gitolite anyway
and since my repo is from git-svn, my commit hashes don't match GitHub
anyway. I'd say make it right and I (we?) can re-clone from the the new
gitolite repo once the transfer is
Yawar Amin yawar.a...@gmail.com writes:
Personally, I feel that it's important to have the history correct,
even if it means resetting and invalidating the existing repos.
[...]
Yes, this is a good opportunity to fix the history. We can simply delete
On Jan 22, 2013, at 7:04 AM, Geert Janssens janssens-ge...@telenet.be wrote:
What steps would your recommend to reattach private branches ? With my
(limited) git knowledge I would only know how to export (git format-patch)
from the old repo and import (git am) in the new clone. Is there a
On 22-01-13 17:41, John Ralls wrote:
On Jan 22, 2013, at 7:04 AM, Geert Janssens janssens-ge...@telenet.be wrote:
What steps would your recommend to reattach private branches ? With my
(limited) git knowledge I would only know how to export (git format-patch) from
the old repo and import
Geert Janssens janssens-ge...@telenet.be writes:
On 22-01-13 17:41, John Ralls wrote:
Can we have the gitolite repo available for a few days to test out
procedures like this before we recreate the Github repo so that we
can have good instructions on the wiki page?
Sure, it's easy to set up
On Jan 22, 2013, at 9:00 AM, Geert Janssens janssens-ge...@telenet.be wrote:
On 22-01-13 17:41, John Ralls wrote:
On Jan 22, 2013, at 7:04 AM, Geert Janssens janssens-ge...@telenet.be
wrote:
What steps would your recommend to reattach private branches ? With my
(limited) git knowledge I
On 22-01-13 16:16, Yawar Amin wrote:
Hi folks,
On 2013-01-22, at 9:51, John Ralls jra...@ceridwen.us wrote:
On Jan 22, 2013, at 5:30 AM, Derek Atkins warl...@mit.edu wrote:
[...]
Maybe.. Here's the bigger issue, if I found issues/bugs in John's
svn-git conversion, what do we do? (and
Hi Geert,
On 2013-01-22 12:25, Geert Janssens wrote:
[...]
Just out of curiosity, what's the size of your private history to
convert ?
The only significant work I have is my fork on GitHub
(yawaramin/gnucash-docs). Other than that, a few throwaway learning
experiments
Regarding svn, it
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't know how to
fix.
I did:
git clone url
git svn init --stdlayout file:///repo/gnucash-docs
git-update
git-svn-mirror update .
After doing a bunch of
On Jan 21, 2013, at 6:11 AM, Derek Atkins warl...@mit.edu wrote:
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't know how to
fix.
I did:
git clone url
git svn init --stdlayout
John Ralls jra...@ceridwen.us writes:
I did:
git clone url
git svn init --stdlayout file:///repo/gnucash-docs
git-update
git-svn-mirror update .
Yes, the [svn2git] and [svn] sections are normally set up by
git-svn-mirror when starting from scratch.
So am I not supposed to add those
On Jan 21, 2013, at 8:33 AM, Derek Atkins warl...@mit.edu wrote:
John Ralls jra...@ceridwen.us writes:
I did:
git clone url
git svn init --stdlayout file:///repo/gnucash-docs
git-update
git-svn-mirror update .
Yes, the [svn2git] and [svn] sections are normally set up by
Hi Derek,
On 2013-01-21, at 9:11, Derek Atkins warl...@mit.edu wrote:
Hey all,
Geert and I were working over the weekend to try to set up an svn-git
mirror on code. Alas, I seem to have an issue that I don't know how to
fix.
I don't know gitolite, but wouldn't it work if you simply
51 matches
Mail list logo
