Subject: Developers of Sympa
List archive
re[2]: [sympa-dev] Patch to make LDAP login behaviour more predictible
- From: Flack Maguire <address@concealed>
- To: David Verdin <address@concealed>, <address@concealed>
- Subject: re[2]: [sympa-dev] Patch to make LDAP login behaviour more predictible
- Date: Thu, 3 Sep 2009 14:52:26 -0700
Hi David,
I was just curious
if there had been any talk on the core team
of moving over to one of the distributed
version control systems (DVCS) like Git,
Bazaar, or Mercurial.
Married up to these
are code hosting services such as Launchpad
and GitHub. But, I think your team
has more than covered the issues such as
a wiki, bug tracking, etc. so I would imagine
they would not be a substantial value add.
Still, the DVCS
tools themselves are growing in popularity
for the flexibility they provide to global
efforts and can be used completely outside
of the hosting services.
Do let me openly
acknowledge that it is extremely easy
for any of us to come up with ideas like
this when it is not us implementing the idea.
And, I will be the first to say that my particular
group has gained far more from Sympa than
we have given at this date which is something
we hope & plan to change as we go farther
with Sympa.
Cheers,
Flack
>>Hi Paul!
>>
>> Well that two files properties... That's a problem I want to fix very soon, but as it is not that
>> big of a problem, I always had something more urgent to do until now.
>> Actually, the properties changes for these two files regards the svn:mergeinfo properties only.
>>
>> A little background can help you understand the situation: There are 6 active SVN branches (in
>> addition to the main development trunk) for now in the Sympa project. Two stabilization branches
>> and four side projects. When we fix a bug, it is wise to transfer the bug fix to all the branches
>> to avoid a too great divergence from the trunk. It helps the fusion once the work on a branch is
>> over and needs to be transferred to the trunk. Until recently, we used manual patches. But the
>> merge option in SVN (> 1.5) is so easy to use that we changed our habits, and so far it works
>> great.
>>
>> Safe for those two...
>>
>> Since the first time we changed the way we handle the different development branches of the Sympa
>> subversion repository, there has always been a discrepancy between a branch and another, whatever
>> branch we work on, for these files only,on the svn:merge property only. This has no impact at all
>> on the Sympa code or on the efficiency of the merges, but they keep appearing in the commit
>> summaries because of it, and it's becoming annoying.
>>
>> I'll fix that right as soon as possible, but that probably implies manually setting the svn:merge
>> property for these files on all the Sympa branches.
>>
>> Life is pain... -)
>>
>> Regards,
>>
>> David
>>
>> Paul Menzel a écrit : Dear David, Am Donnerstag, den 03.09.2009, 12:26 +0200 schrieb David
>> Verdin: […] You're both right! We applied your patch to both 6.0 branch and the development
>> trunk. Thanks for submitting it! Big thanks fromme too. David commited your patch in revision
>> 6168. David, the commit changed also the properties of two files. Was that intentional? Bests,
>> Paul [1] http://sourcesup.cru.fr/cgi/viewvc.cgi?view=rev&revision=6168
>> -- David Verdin Comité réseau des universités
>>
>> Well that two files properties... That's a problem I want to fix very soon, but as it is not that
>> big of a problem, I always had something more urgent to do until now.
>> Actually, the properties changes for these two files regards the svn:mergeinfo properties only.
>>
>> A little background can help you understand the situation: There are 6 active SVN branches (in
>> addition to the main development trunk) for now in the Sympa project. Two stabilization branches
>> and four side projects. When we fix a bug, it is wise to transfer the bug fix to all the branches
>> to avoid a too great divergence from the trunk. It helps the fusion once the work on a branch is
>> over and needs to be transferred to the trunk. Until recently, we used manual patches. But the
>> merge option in SVN (> 1.5) is so easy to use that we changed our habits, and so far it works
>> great.
>>
>> Safe for those two...
>>
>> Since the first time we changed the way we handle the different development branches of the Sympa
>> subversion repository, there has always been a discrepancy between a branch and another, whatever
>> branch we work on, for these files only,on the svn:merge property only. This has no impact at all
>> on the Sympa code or on the efficiency of the merges, but they keep appearing in the commit
>> summaries because of it, and it's becoming annoying.
>>
>> I'll fix that right as soon as possible, but that probably implies manually setting the svn:merge
>> property for these files on all the Sympa branches.
>>
>> Life is pain... -)
>>
>> Regards,
>>
>> David
>>
>> Paul Menzel a écrit : Dear David, Am Donnerstag, den 03.09.2009, 12:26 +0200 schrieb David
>> Verdin: […] You're both right! We applied your patch to both 6.0 branch and the development
>> trunk. Thanks for submitting it! Big thanks fromme too. David commited your patch in revision
>> 6168. David, the commit changed also the properties of two files. Was that intentional? Bests,
>> Paul [1] http://sourcesup.cru.fr/cgi/viewvc.cgi?view=rev&revision=6168
>> -- David Verdin Comité réseau des universités
-
[sympa-dev] Patch to make LDAP login behaviour more predictible,
Matthias Warkus, 09/01/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/03/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
Paul Menzel, 09/03/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/03/2009
- [sympa-dev] Merging and change of svn:mergeinfo property (was:, Paul Menzel, 09/03/2009
-
re[2]: [sympa-dev] Patch to make LDAP login behaviour more predictible,
Flack Maguire, 09/03/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/04/2009
-
[sympa-dev] Using distributed version control systems (Git, Bazaar, Mercurial)(was: Patch to make LDAP login behaviour more predictible),
Paul Menzel, 09/04/2009
- Re: [sympa-dev] Using distributed version control systems (Git, Bazaar,, David Verdin, 09/04/2009
- re[2]: [sympa-dev] Patch to make LDAP login behaviour more predictible, Flack Maguire, 09/05/2009
-
[sympa-dev] Using distributed version control systems (Git, Bazaar, Mercurial)(was: Patch to make LDAP login behaviour more predictible),
Paul Menzel, 09/04/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/04/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/03/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
Paul Menzel, 09/03/2009
-
Re: [sympa-dev] Patch to make LDAP login behaviour more predictible,
David Verdin, 09/03/2009
Archive powered by MHonArc 2.6.19+.