Re: Problem with GitHub repos ?

[Francois-Xavier Le Bail <fx.lebail () yahoo com>]

> From: Guy Harris <guy () alum mit edu>

> On Apr 12, 2014, at 1:48 AM, Francois-Xavier Le Bail <fx.lebail () yahoo com> 
> wrote:

> >  the images are here :
> >  https://gist.github.com/fxlb/10525029 
>
> Yes, those branches are branches that exist in the bpf.tcpdump.org repositories; 
> I guess pushing from there to GitHub causes the GitHub repository to have them 
> as well.
>
> Most of them are not worthy of being run through Travis, at least as far as 
> I'm concerned; can it be configured to build only the trunk (master) for 
> now?  (I think the next releases will be 1.6/4.6, coming from the trunk; once 
> those are branched, the 1.6 and 4.6 branches should probably be run through 
> Travis as well.)

1) Are the branches marked "merged into master" (tcpdump: bare and origin ; libpcap : bare and origin) still useful? 
Otherwise, they could be deleted.

2)  For all branches, first question is : will new commits be pushed into this branch ?
if no : no more Travis problems.

3) The other question is: is there a '.travis.yml' file in the branch ?
if no :
a) No correct builds.
b) We cannot use the 'except' keyword for blacklist branches, nor 'only' keyword for whitelist branches.

So remain branches which have to evolve and have no '.travis.yml':
a) We need to add a '.travis.yml' file in the branch.
b) If they must not be build by Travis, one of the two aformentioned keywords could be used.

Same for new branches.

Hope this help.

_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers