Re: splitting up kdebase in git
Hi, On 02/11/11 22:44, Ingo Klöcker wrote: >> Since that location in SVN is now a bit obscure, perhaps we should >> create a new SVN module called trunk/KDE/kdebase-wallpapers. > kde-wallpapers? Because ... > >> The context here is that: SVN is just better then Git at storing >> stuff like wallpapers, so I think we should consider it as the best >> longterm solution for big binary blobs. But wallpapers are required >> by kdebase-workspace. > ... because kdebase/workspace became kde-workspace in Git. I would like to underline that they are our default wallpapers (they used to be part of kdebase and they musn't be confused with extras wallpapers in kdeartwork). Anyway trunk/KDE/kde-wallpapers should be ok too. Bye, Davide Bettio. signature.asc Description: OpenPGP digital signature
www/sites/www/announcements/changelogs
SVN commit 1220053 by pino: upate the changelog.xsl to support gitweb links kind of abstract the "web $vcs" name and link generation, deducing the repository type from the revision string: - less than 7 chars, svn - 40 chars, git additionally, introduce a new "reponame" attribute for "module", "product", and "component" tags, to allow setting the repository name (the most specific one wins); if not specified, the default behaviour is to use the component or product name. should hopefully not break anything, in case just let me know CCMAIL: kde-core-devel@kde.org M +3 -3 DOCS M +5 -1 changelog.dtd M +97 -5 changelog.xsl --- trunk/www/sites/www/announcements/changelogs/DOCS #1220052:1220053 @@ -53,13 +53,13 @@ Divisions - - + An SVN module. If possible, make sure the lowercase form of the "name" attribute is the exact name of the module in SVN (this makes the 'rev' attribute work - see below). - + An application or other component which forms the toplevel in an SVN module. Again, make sure that the lowercase form of the name attribute is as it appears in SVN if you want the 'rev' attribute to work. The homepage attribute is an optional URL of the product's homepage. - + A component within a . Change types --- trunk/www/sites/www/announcements/changelogs/changelog.dtd #1220052:1220053 @@ -15,6 +15,7 @@ - + - - + + + + + + + + + + + + + + + + + + + + + + + + + + - See SVN commit + See + + + + commit - See SVN commits + See + + + + commits , @@ -201,7 +233,10 @@ and - + + + + . @@ -230,5 +265,62 @@ + + + +svn +git + + +Unknown VCS for commit ''! + + + + + + + + +SVN +Git + + +Unknown VCS type ''! + + + + + + + + + + + + + + + + + + + + + + Git commit without 'reponame' attribute! + + + + + + +Unknown VCS type ''! + + + + + http://websvn.kde.org + http://commits.kde.org +
Re: reminder: git workflow irc meeting on Sunday
- Original Message - > hi all... > > just a quick and friendly reminder that the git workflow irc meeting > is on for > Sunday the 13th starting at 20:00 UTC on irc.freenote.net in #kde-git. > > see you all there! :) > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Development Frameworks Hi, Is there an agenda for the meeting, or some documentation? If everyone gets a chance to explain their preferred git workflow and we are going to be a discussion afterwards and pick one, I bet this is a meeting that will take forever with loads of frustration and chaos. Any thoughts on that? Best, -- Tom Albers KDE Sysadmin
Re: splitting up kdebase in git
- Original Message - > Hi, > > Our default wallpapers used to be part of kdebase/workspace, but > during > the git migration they've been removed from workspace due the size of > that directory. > Wallpapers can't be kept in a git repository because every time a git > repository is cloned all the history (including old wallpapers) is > cloned. So actually wallpapers are nowhere, should we move wallpapers > back to trunk/KDE/kdebase/workspace? > > Bye, > Davide Bettio. Maybe just a tarball somewhere? SVN won't stay around, so we need another solution i think. Best, -- Tom Albers KDE Sysadmin
Re: reminder: git workflow irc meeting on Sunday
On Saturday 12 February 2011 18:53:11 Tom Albers wrote: > Hi, > > Is there an agenda for the meeting, or some documentation? If everyone gets > a chance to explain their preferred git workflow and we are going to be a > discussion afterwards and pick one, I bet this is a meeting that will take > forever with loads of frustration and chaos. Any thoughts on that? > > Best, http://community.kde.org/20110213_GitWorkflowAgenda
Re: splitting up kdebase in git
On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: > - Original Message - > > > Hi, > > > > Our default wallpapers used to be part of kdebase/workspace, but > > during > > the git migration they've been removed from workspace due the size of > > that directory. > > Wallpapers can't be kept in a git repository because every time a git > > repository is cloned all the history (including old wallpapers) is > > cloned. So actually wallpapers are nowhere, should we move wallpapers > > back to trunk/KDE/kdebase/workspace? > > > > Bye, > > Davide Bettio. > > Maybe just a tarball somewhere? SVN won't stay around, so we need another > solution i think. I thought we were keeping SVN around for translations? Or will they simply migrate after the rest of the modules have? Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part.
Re: splitting up kdebase in git
- Original Message - > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: > > - Original Message - > > > > > Hi, > > > > > > Our default wallpapers used to be part of kdebase/workspace, but > > > during > > > the git migration they've been removed from workspace due the size > > > of > > > that directory. > > > Wallpapers can't be kept in a git repository because every time a > > > git > > > repository is cloned all the history (including old wallpapers) is > > > cloned. So actually wallpapers are nowhere, should we move > > > wallpapers > > > back to trunk/KDE/kdebase/workspace? > > > > > > Bye, > > > Davide Bettio. > > > > Maybe just a tarball somewhere? SVN won't stay around, so we need > > another > > solution i think. > > I thought we were keeping SVN around for translations? Or will they > simply > migrate after the rest of the modules have? I personally have no intention to maintain two revision control systems. -- Tom Albers KDE Sysadmin
Re: splitting up kdebase in git
On Saturday 12 February 2011, Tom Albers wrote: > - Original Message - > > > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: > > > - Original Message - > > > > > > > Hi, > > > > > > > > Our default wallpapers used to be part of kdebase/workspace, but > > > > during > > > > the git migration they've been removed from workspace due the size > > > > of > > > > that directory. > > > > Wallpapers can't be kept in a git repository because every time a > > > > git > > > > repository is cloned all the history (including old wallpapers) is > > > > cloned. So actually wallpapers are nowhere, should we move > > > > wallpapers > > > > back to trunk/KDE/kdebase/workspace? > > > > > > > > Bye, > > > > Davide Bettio. > > > > > > Maybe just a tarball somewhere? SVN won't stay around, so we need > > > another > > > solution i think. > > > > I thought we were keeping SVN around for translations? Or will they > > simply > > migrate after the rest of the modules have? > > I personally have no intention to maintain two revision control systems. Maybe something has to be done in git ? (basically all tools which get introduced to KDE have a fixing/feature addition phase initially ;-) Alex
Re: splitting up kdebase in git
Hi, On 02/12/11 20:12, Tom Albers wrote: > Maybe just a tarball somewhere? SVN won't stay around, so we need another > solution i think. > So probably we have to move it to a wallpapers git repository, anyway until SVN is active we can continue to use it. Bye, Davide Bettio. signature.asc Description: OpenPGP digital signature
Re: splitting up kdebase in git
On Saturday 12 February 2011, Tom Albers wrote: > - Original Message - > > > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: > > > - Original Message - > > > > > > > Hi, > > > > > > > > Our default wallpapers used to be part of kdebase/workspace, > > > > but during > > > > the git migration they've been removed from workspace due the > > > > size of > > > > that directory. > > > > Wallpapers can't be kept in a git repository because every time > > > > a git > > > > repository is cloned all the history (including old wallpapers) > > > > is cloned. So actually wallpapers are nowhere, should we move > > > > wallpapers > > > > back to trunk/KDE/kdebase/workspace? > > > > > > > > Bye, > > > > Davide Bettio. > > > > > > Maybe just a tarball somewhere? SVN won't stay around, so we need > > > another > > > solution i think. > > > > I thought we were keeping SVN around for translations? Or will they > > simply > > migrate after the rest of the modules have? > > I personally have no intention to maintain two revision control > systems. I understood that SVN would stay indefinitely (read-only) because the Git repos do not carry the full history. (Of course a read-only SVN won't really help with the wallpapers.) Regards, Ingo signature.asc Description: This is a digitally signed message part.
