bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saint Germain <saint...@gmail.com>
Subject Re: Guidance needed to contribute to Bloodhound
Date Thu, 14 Nov 2013 08:11:35 GMT
On Wed, 13 Nov 2013 16:43:37 -0500, Olemis Lang <olemis@gmail.com>
wrote :

> >
> > Will bloodhound-mq contains only the patches or also the trunk ?
> >
> 
> That depends on whether you clone vs qclone it . In the first case
> you'll get patches repository (I guess) . If you qclone it then
> you'll get everything properly setup .
> 
> I don't see the difference between bloodhound-tlp qnd
> bloodhound_hggit/
> > if they are synchronized, shouldn't they be the same ?
> >
> 
> hggit copies are different to hgsubversion copies .
> 
> 
> > If not which one should I use to apply the patches ?
> >
> 
> bloodhound-mq
> 

Currently last commit on trunk in bloodhound-mq is from 14th january,
so I will wait that you synchronize it with the official trunk to
continue.

> >
> > Is there a reason why you managed all the patches in a different
> > branch ?
> >
> 
> 1. historical reasons - that's relatively the same thing that osimons
> did for trac rpc plugin
> 2. reuse - sometimes patches for one ticket are required to fix
> another ticket ;
>     this is handled by merging both branches and , since there's also
> a folder e.g. t123/
>     conflicts are limited to series file , which contains patch order
> 3. it's possible to switch back and forth to work on multiple tickets
> 
> I haven't seen this approach recommended when I was looking at MQ
> > tutorial.
> >
> 
> it's not written in any book (... that I know ...)
> 

Ok thanks for the explanations.

> > You seem to have a nice workflow, so I
> > am trying to copy it ! ;-)
> >
> 
> © copyright osimons + olemis

Maybe we should write a wiki page about it ?
On the front page of Bitbukcet bloodhound-mq maybe ?

Thanks !

Mime
View raw message