6 Nov
2011
6 Nov
'11
11:45 p.m.
All,
Just a quick reminder that the Trinity source repositories (but not the
packaging repository) remain FROZEN at this time while I complete the SVN
to GIT move and get all of the support systems up and running again. All
new account requests should sent AFTER the repositories have been thawed.
Also, please remember to remove the nightly build repository lines from
your /etc/apt/sources.list file. Within the next few days the contents of
that repository will become highly unstable and in all likelihood
uninstallable as well.
Now is the time when all developers should be combing through the bug
tracker and fixing bugs, uploading their patches to the bug report as
attachments.
Tim
7 Nov
7 Nov
12:18 a.m.
New subject: [trinity-devel] SVN-->GIT move
2011/11/7 Timothy Pearson <kb9vqf(a)pearsoncomputing.net>et>:
All,
Just a quick reminder that the Trinity source repositories (but not the
packaging repository) remain FROZEN at this time while I complete the SVN
to GIT move and get all of the support systems up and running again. All
new account requests should sent AFTER the repositories have been thawed.
Also, please remember to remove the nightly build repository lines from
your /etc/apt/sources.list file. Within the next few days the contents of
that repository will become highly unstable and in all likelihood
uninstallable as well.
Now is the time when all developers should be combing through the bug
tracker and fixing bugs, uploading their patches to the bug report as
attachments.
Tim
Do You plan on keeping the frozen code in the SVN and updating it on
next froze, or You host source tarballs somewhere? It seems like a
good idea to keep the stable code in the svn to me.
12:24 a.m.
New subject: [trinity-devel] SVN-->GIT move
2011/11/7 Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>et>:
I did keep the 3.5.13 code in SVN, however as the KDE project is (AFAIK)
trying to get rid of its SVN server I don't know how feasible keeping the
stable code in SVN is going to be.
Tim
All,
Just a quick reminder that the Trinity source repositories (but not the
packaging repository) remain FROZEN at this time while I complete the
SVN
to GIT move and get all of the support systems up and running again.
All
new account requests should sent AFTER the repositories have been
thawed.
Also, please remember to remove the nightly build repository lines from
your /etc/apt/sources.list file. Within the next few days the contents
of
that repository will become highly unstable and in all likelihood
uninstallable as well.
Now is the time when all developers should be combing through the bug
tracker and fixing bugs, uploading their patches to the bug report as
attachments.
Tim
Do You plan on keeping the frozen code in the SVN and updating it on
next froze, or You host source tarballs somewhere? It seems like a
good idea to keep the stable code in the svn to me. 
12:26 a.m.
New subject: [trinity-devel] SVN-->GIT move
On Sun, Nov 6, 2011 at 19:24, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net> wrote:
I did keep the 3.5.13 code in SVN, however as the KDE project is (AFAIK)
trying to get rid of its SVN server I don't know how feasible keeping the
stable code in SVN is going to be.
Tim
After the import, you should tag the last commit each of the
repositories as 3.5.13.
This way, Git knows that it's a release, and it'll separate that from the rest.
(And if gitweb likes to be tag-happy, it might generate tarballs...)
--
later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu
9 Nov
9 Nov
4:37 p.m.
In article <2570a0110de40f405eb18ee935957a12.squirrel(a)vali.starlink.edu>du>,
Timothy Pearson <trinity-devel(a)lists.pearsoncomputing.net> wrote:
I did keep the 3.5.13 code in SVN, however as the KDE
project is (AFAIK)
trying to get rid of its SVN server I don't know how feasible keeping the
stable code in SVN is going to be.
Whilst you're beating the git repo into shape, I updated from svn.
I found that changing the code's root directory in svn to 3.5.13_frozen
has meant that the svn:externals are now wrong. The paths should be
changed from branches/trinity/* to branches/trinity/3.5.13_frozen/*
Is it worth doing a quick fix there if the repo will stay around ?
Nick
--
Serendipity: http://www.leverton.org/blosxom (last update 29th March 2010)
"The Internet, a sort of ersatz counterfeit of real life"
-- Janet Street-Porter, BBC2, 19th March 1996
4545
days inactive
4548
days old
4 comments
4 participants
participants (4)
-
L0ner sh4dou -
Nick Leverton -
Robert Xu -
Timothy Pearson