On Tuesday 01 February 2011 21:37:26 Aaron J. Seigo wrote:
> so i'd like to suggest that we gather on irc in the near future and hammer
> this stuff out. weekends tend to be better for many it seems, so i've put
> up a doodle here:
Fantastic :-) Just to point out that FOSDEM is this weekend, so m
On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote:
> * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy
>
i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in
particular point 8 of the rules. the point it makes is independent from
using git (in fact, we ha
On Wednesday 02 February 2011 09:19:29 Oswald Buddenhagen wrote:
> On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote:
> > * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy
>
> i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in
> particular point 8 of t
On Wed, Feb 2, 2011 at 08:45, John Layt wrote:
> On Wednesday 02 February 2011 09:19:29 Oswald Buddenhagen wrote:
>> i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in
>> particular point 8 of the rules. the point it makes is independent from
>> using git (in fact, we have a si
Zitat von John Layt :
On Wednesday 02 February 2011 09:19:29 Oswald Buddenhagen wrote:
On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote:
> * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy
i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in
particu
On Wednesday 02 February 2011, Oswald Buddenhagen wrote:
> On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote:
> > * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy
>
> i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in
> particular point 8 of the rules.
On Tuesday 01 February 2011, Aaron J. Seigo wrote:
> hi everyone ...
>
> with git having finally arrived more-or-less, we find ourselves without a
> well defined work flow for kdelibs (and by extension other KDE
> repositories)
>
> i don't think we can or should hope and pray that our sysadmins wil
On Wednesday, February 2, 2011, Alexander Neundorf wrote:
> * for any change, create a topic branch from master
> * work in the branch...
in cmake development, how do developers find each other's branches to check on
works-in-progress, collaborate, etc? are they pushed to a shared repository
som
On Wednesday 02 February 2011, i...@michael-jansen.biz wrote:
> Zitat von John Layt :
>
> > On Wednesday 02 February 2011 09:19:29 Oswald Buddenhagen wrote:
> >> On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote:
> >> > * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy
> >
On Wednesday 02 February 2011, Aaron J. Seigo wrote:
> On Wednesday, February 2, 2011, Alexander Neundorf wrote:
> > * for any change, create a topic branch from master
> > * work in the branch...
>
> in cmake development, how do developers find each other's branches to check
> on
> works-in-pro
Quoting Boudewijn Rempt :
I like it as well. How can I make sure calligra hackers get to see
this when they
try to commit?
Just create a text file named ".commit-template" in your repo's root
folder with the template :)
Cheers,
Artur
---
Quoting Boudewijn Rempt :
I like it as well. How can I make sure calligra hackers get to see
this when they
try to commit?
Ah and add:
[commit]
template = .commit-template
to your git config file
(I forgot this in the other mail :)
Cheers,
Artur
PS: thanks Alexis :P
On Wednesday 02 February 2011, Artur de Souza wrote:
> Quoting Boudewijn Rempt :
> > I like it as well. How can I make sure calligra hackers get to see
> > this when they
> > try to commit?
>
> Ah and add:
>
> [commit]
> template = .commit-template
>
> to your git config file
>
> (I
On Wednesday, February 2, 2011, Boudewijn Rempt wrote:
> In calligra, i was surprised to see people taking to branching like pigs to
> muck or fish to water.
yeah, they are awesome :)
> We now have 37 feature branches, of which several
> have merged to master after review already. There's a simpl
On Wednesday 02 February 2011, Aaron J. Seigo wrote:
> > -- and it all works out very well. Master is
>
> is everyone pushing their branches to the main repository, or keeping them in
> separate cloned repositories?
Yes, to the main repository. No public clones. We might have to rething that
w
On Wednesday, February 2, 2011, Boudewijn Rempt wrote:
> On Wednesday 02 February 2011, Aaron J. Seigo wrote:
> > > -- and it all works out very well. Master is
> >
> > is everyone pushing their branches to the main repository, or keeping
> > them in separate cloned repositories?
>
> Yes, to the
On Wednesday 02 February 2011, Aaron J. Seigo wrote:
> On Wednesday, February 2, 2011, Alexander Neundorf wrote:
> > * for any change, create a topic branch from master
> > * work in the branch...
>
> in cmake development, how do developers find each other's branches to check
> on works-in-progress
On Tuesday, February 1, 2011, Aaron J. Seigo wrote:
> hi everyone ...
>
> with git having finally arrived more-or-less, we find ourselves without a
> well defined work flow for kdelibs (and by extension other KDE
> repositories)
>
> i don't think we can or should hope and pray that our sysadmins
On Tuesday 01 February 2011, Aaron J. Seigo wrote:
> * 3rd party examples we can learn from:
> http://public.kitware.com/Wiki/Git/Workflow/Topic
> Qt?
http://wiki.videolan.org/Git
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Ko
On Friday, February 4, 2011, you wrote:
> On Tuesday 01 February 2011, Aaron J. Seigo wrote:
> > * 3rd party examples we can learn from:
> > http://public.kitware.com/Wiki/Git/Workflow/Topic
> > Qt?
>
> http://wiki.videolan.org/Git
thanks; added to
http://community.kde.or
20 matches
Mail list logo
