Hi Sandro,
On Wed, Aug 27, 2014 at 09:13:32AM +0100, Sandro Tosi wrote:
> On Mon, Aug 25, 2014 at 10:00 PM, Barry Warsaw wrote:
> > Here's the page I mentioned regarding a *proposed* transition plan to using
> > git for team packages. It's more or less a brain dump right now, and don't
> > feel
❦ 27 août 2014 18:11 -0700, Nikolaus Rath :
>> 2. Sometimes I make repeated mistakes when building a package; under
>> subversion I have to make a new commit for each one before testing.
>
> Why is that? I'm testing my uncommitted changes with
>
> svn-buildpackage --svn-ignore-new --svn-builder
Brian May writes:
> 2. Sometimes I make repeated mistakes when building a package; under
> subversion I have to make a new commit for each one before testing.
Why is that? I'm testing my uncommitted changes with
svn-buildpackage --svn-ignore-new --svn-builder=pdebuild
and it seems to work very
On 27 August 2014 18:13, Sandro Tosi wrote:
>
> is there anything else so "attractive" about git?
>
I can think of two benefits off the top of my head.
1. Subversion "tags" don't work for me. I think this is because I have
deleted files since the last tag, I posted a message here, nobody was ab
Hi Sandro,
On Aug 27, 2014, at 09:13 AM, Sandro Tosi wrote:
>nothing against your effort or experiments (I really appreciate it),
>but I still don't see what is the advantages of moving to Git.
There's "moving to git" and "moving to a dvcs" - slightly different, but
related issues. For me, movi
On 2014-08-27 01:41, Antoine Musso wrote:
> Le 27/08/2014 10:13, Sandro Tosi a écrit :
>
>> Offline commits? how many time (for real..) you badly needed it? i
>> guess so few that if you (for one time) just do a big commit instead
>> of a storm of micro commit the world wont stop
>
> As a side ef
On Aug 27, 2014, at 10:30 AM, Antoine Musso wrote:
>Coupled with a pre review software such as Gerrit, that let one propose
>a patchset, have the build result displayed and iterate until the patch
>is ready to land in the branch.
I personally love such gated systems when working on software. The
> This discussion has been had many times before over many years. Of late, the
and it was never driven by the problems we have, but just by "oh look
how cool git is", "everybody else is using it, and i'm too lazy to
learn a new tool" arguments.
> difficulty in switching VCS has been the blocker.
Hi Sandro,
> I rarely need to use log, and I used to work on the svn repo on a 56k
[..]
that you rarely use log is (a) not relevant to the people who would use it
and (b) quite possibly highly influenced by the fact that svn log is so slow
and painful. Remember that the tool can shape the user.
On 2014-08-27 at 10:40:40 +0200, Raphael Hertzog wrote:
> On Wed, 27 Aug 2014, Sandro Tosi wrote:
> > It seems to me like very vocal Git fanatics, who refuse to touch any
> > package which is not maintained in Git (-.-), are pushing and pushing
> > to that VCS without any clear advantage.
> You mig
On Wed, 27 Aug 2014, Sandro Tosi wrote:
> like true contributors are those using svn right now. and what about
> the majority of contributors now? we should change just because maybe,
> eventually, if we're lucky we'll attract more contributors? saying "I
> won't contribute to your team if you don'
On Wed, Aug 27, 2014 at 9:41 AM, Antoine Musso wrote:
> Le 27/08/2014 10:13, Sandro Tosi a écrit :
>
>> Offline commits? how many time (for real..) you badly needed it? i
>> guess so few that if you (for one time) just do a big commit instead
>> of a storm of micro commit the world wont stop
>
>
On Wed, Aug 27, 2014 at 9:40 AM, Raphael Hertzog wrote:
> Hi Sandro,
>
> On Wed, 27 Aug 2014, Sandro Tosi wrote:
>> It seems to me like very vocal Git fanatics, who refuse to touch any
>> package which is not maintained in Git (-.-), are pushing and pushing
>> to that VCS without any clear advanta
Le 25/08/2014 23:00, Barry Warsaw a écrit :
> Here's the page I mentioned regarding a *proposed* transition plan to using
> git for team packages. It's more or less a brain dump right now, and don't
> feel like you need to read it before the DC14 session.
>
> https://wiki.debian.org/Python/GitPac
Le 27/08/2014 10:13, Sandro Tosi a écrit :
> Offline commits? how many time (for real..) you badly needed it? i
> guess so few that if you (for one time) just do a big commit instead
> of a storm of micro commit the world wont stop
As a side effect, that also mean you don't have to use a potenti
Le 26/08/2014 20:36, Hans-Christoph Steiner a écrit :
> * the git-buildpackage workflow is really quite wonderful and reasonably
> flexible, I highly recommend it, and I think it will improve the productivity
> of this team.
Hello,
At Wikimedia we solely use git-buildpackage. DD Michael Prokop wr
Hi Sandro,
On Wed, 27 Aug 2014, Sandro Tosi wrote:
> It seems to me like very vocal Git fanatics, who refuse to touch any
> package which is not maintained in Git (-.-), are pushing and pushing
> to that VCS without any clear advantage.
You might dismiss those people but you're speaking of true c
Hi Barry,
thanks for your work!
On Mon, Aug 25, 2014 at 10:00 PM, Barry Warsaw wrote:
> Here's the page I mentioned regarding a *proposed* transition plan to using
> git for team packages. It's more or less a brain dump right now, and don't
> feel like you need to read it before the DC14 session
On 2014-08-26 20:04, Stuart Prescott wrote:
>>> I eventually gave up and used git-import-dscs -- debsnap.
>>>
>>> That said -- all the above experience was with full-source svn repos. I
>>> would anticipate that the debian/-only repos would be easier to migrate as
>>> they are much simpler, but the
Hi Barry,
>>I eventually gave up and used git-import-dscs -- debsnap.
>>
>>That said -- all the above experience was with full-source svn repos. I
>>would anticipate that the debian/-only repos would be easier to migrate as
>>they are much simpler, but then the new git repo would also be
>>debian/
Hi Stuart,
On Aug 27, 2014, at 11:57 AM, Stuart Prescott wrote:
>I eventually gave up and used git-import-dscs -- debsnap.
>
>That said -- all the above experience was with full-source svn repos. I would
>anticipate that the debian/-only repos would be easier to migrate as they are
>much simpler,
Hi Barry,
thanks for this write-up.
An open question remains what to do about the current history that is in
svn. My experience of doing this is as follows:
* For many repos, svn-all-fast-export does an excellent job of turning a
complete svn history into something that looks identical to what
On Aug 26, 2014, at 02:36 PM, Hans-Christoph Steiner wrote:
>I think this plan makes a lot of sense. I'll just throw in my two bits for a
>couple of other points:
Cool.
>* the git-buildpackage workflow is really quite wonderful and reasonably
>flexible, I highly recommend it, and I think it wil
I think this plan makes a lot of sense. I'll just throw in my two bits for a
couple of other points:
* the git-buildpackage workflow is really quite wonderful and reasonably
flexible, I highly recommend it, and I think it will improve the productivity
of this team.
* Vcs-Git and Vcs-Browser s
Here's the page I mentioned regarding a *proposed* transition plan to using
git for team packages. It's more or less a brain dump right now, and don't
feel like you need to read it before the DC14 session.
https://wiki.debian.org/Python/GitPackaging
Food for thought and discussion.
-Barry
sign
25 matches
Mail list logo
